SEO Insights: Unpredictable WordPress Redirects, Customized API Data, and CDN Recommendations

Try Our Free Tools!
Master the web with Free Tools that work as hard as you do. From Text Analysis to Website Management, we empower your digital journey with expert guidance and free, powerful tools.

Pulse Weekly Update

This week’s edition of Pulse brings forth significant developments including a new WordPress default requiring your consideration, fresh data availability from Search Console via its API, and the ongoing debate regarding which entities—Googlebot, artificial intelligence agents, or Google’s own operations—will be permitted access.

The impending release of WordPress 7.2 will unveil a default /random/ redirect feature, while Google has enriched the Search Console API with branded data.

Additionally, Google disclosed the referrer values associated with its traffic and elaborated on how transitioning to a Content Delivery Network (CDN) could inadvertently obstruct Googlebot.

Furthermore, Ask Maps has begun reaching out to local businesses, and United Airlines has incorporated guidelines regarding AI agents into its terms and conditions.

WordPress 7.2 Launches /Random/ Redirect As Default Feature

WordPress 7.2, slated for release on December 8, will feature a /random/ redirect, which is enabled by default to direct users to randomly selected published articles. Notably, there is no option to disable this feature through the dashboard settings.

Key insights: As outlined in the developer note, the /random/ function selects both standard posts and custom post types that are publicly queryable and have archives (unless explicitly marked with 'randomable' => false).

Pages and attachments are not included. The feature employs a 302 status code along with an X-Robots-Tag: noindex, follow HTTP header for redirection, excluding this header for the destination post.

Developers can disable this feature using the wp_enable_random_content_redirect filter, although an alternate spelling referenced in the November developer news roundup is not found in the source code.

Implications of This Change

Client testimonials (and other custom post types) may become inaccessible through standard navigation. If a custom post type is eligible, it could be reached via /random/, despite being set to noindex through an SEO plugin.

Prior to the update, assess which post types comply with WordPress’s eligibility standards, and consult a developer about excluding those that should not appear.

Introduction of Branded Query Data in the Search Console API

Utilizing the Search Console API now allows teams to differentiate between branded and non-branded search data without the hassle of maintaining a regex list of their brands.

Key insights: As of November 16, three Performance report features were introduced to the Search Analytics API by Google.

Specifically, the brandedClassification dimension is applicable solely to qualifying properties, with data for this dimension available starting February 21, 2026, per the API reference.

By setting type to webMultimodal, results from Google Lens, Circle to Search on Android, and image uploads can be retrieved.

Additionally, a new filterLists field enables filtering across multiple countries or devices within a single request.

Significance of These Developments

For any reports pertaining to dates prior to February 21, 2026, your existing brand regex will still be required.

Google’s announcement regarding the branded queries filter indicates that “some queries may occasionally be misclassified,” making it essential to cross-verify the API’s outcomes against your regex to identify discrepancies.

Referrer Values for Search, Discover, and Google Images Unveiled

A Google.com referrer provides insights in your analytics regarding visitors sent from Google, yet it does not specify whether the traffic originated from Search, Discover, or Google Images, according to a newly published page on Search Central.

Key insights: Listed on November 12 in Google’s documentation update log, the page states that Google Search employs an origin referrer policy; hence, the header will reveal only the scheme and host without the search query.

Referrals from Discover encompass the values representing the interface where Discover was accessed. Services within the same origin, like Google Images, convey identical values to those from Search and Discover.

Why This Information Is Crucial

To differentiate between clicks from Discover and those from Search, it is advisable to utilize the Discover report available in Search Console rather than relying solely on referrer data.

If Google traffic appears as referral or direct in your analytics, it is recommended to verify whether custom channel rules, referral exclusions, or filters may be reclassifying that traffic.

CDN Transition May Accelerate Googlebot Crawling Pre-Cache

Transitioning to a CDN can expedite Googlebot’s ability to crawl your website prior to the caching process being completed, as noted by Google, with requests directed at your origin server.

Key insights: In a post dated November 11, Search Central articulated that a fast and dependable CDN could gradually enhance a site’s crawl capacity limit, whereas a newly established CDN commences with an empty cache.

The initial access to each URL results in a cache miss, necessitating retrieval from your origin server; crawlers tend to access a significantly higher number of URLs than typical visitors, who usually rely on a limited selection of popular pages.

Furthermore, if site administrators implement blanket bot protections blocking all bots, this may hinder Googlebot’s ability to overcome CAPTCHA challenges. Sustaining such measures could result in the site’s pages gradually disappearing from search results.

Relevance of This Advice

Google recommends allowing verified bots in both CDN and firewall configurations, followed by pre-warming caches by fetching your most frequented URLs preceding the transition of traffic.

Prior to activating bot protections during the migration phase, ensure that the verified-bot settings are duly configured.

Ask Maps Initiates Contact with Local Businesses to Confirm Appointment Availability

Google’s Ask Maps has commenced outreach to various beauty, pet care, automotive, and home-repair businesses across the U.S. to ascertain available appointment slots for customers.

Key insights: In a November 16 blog post, Google announced that Ask Maps enables customers to discover these available appointments online and arrange calls to local businesses, subsequently displaying all available time slots for user selection.

This feature is currently being rolled out on both Android and iOS platforms, with initial availability in the U.S. Google has previously utilized automated calls to assist customers with appointment bookings and confirmations via Google Search and Maps, as detailed in Google’s Business Profile support page.

In the demonstration shared by Google, Ask Maps successfully displayed four available times for a gel manicure that had been confirmed through online inquiry. Some sequences in the demo were shortened and simulated.

Importance of This Initiative

The setting referenced by Google for these automated calls is encapsulated in the “Bookings and inquiries from customers” option found in the Advanced settings of your verified Business Profile.

Nonetheless, Google’s Ask Maps communication does not clarify if calls originated through Ask Maps are governed by this setting.

Therefore, verify your existing configurations and ensure that personnel answering these calls are aware that they represent inquiries from Google on behalf of customers.

United Airlines Establishes Protocol for AI Agents but Permits Open Search Indexing

United Airlines’ recently updated terms of service, as of November 11, allow search engines to index its public-facing pages while requiring explicit written consent for any AI agent engaging in searches, bookings, or purchases via its website or app.

Key insights: The updated terms prohibit the use of data from United’s platforms, such as fares and schedules, for training, refining, or developing an AI model.

As of November 14, United’s robots.txt file does not specifically name any AI crawlers or agents. In a separate report by HUMAN Security from October, it was revealed that Meta’s and OpenAI’s agents accounted for nearly 90% of the agent requests on websites and applications under its protection.

Data from HUMAN Security indicated that Meta’s Muse was responsible for 59% of agent requests, with three OpenAI agents collectively accounting for approximately 30%.

Why This Is Significant

Meta’s Muse does not disclose a user agent suitable for specification in a robots.txt directive, as highlighted by Slobodan Manic in the previous October analysis.

Consequently, whether it gains access is contingent upon established terms and bot protection measures.

Given that Muse generated the highest volume of requests in HUMAN Security’s data, appropriate bot rules can scrutinize some of the signatures within its requests, which were reported to have switched to muse.ai as of November 9.

Peruse our comprehensive report: United Airlines Permits Search Engine Indexing, Mandates Prior Consent from AI Agents, and Analyzes Agent Requests by Meta and OpenAI

Theme of the Week: Dependencies Beyond the SEO Team

Much of the current focus within SEO activities depends on decision-making from teams outside the realm of SEO itself.

Three Scrabble tiles spelling SEO are placed upright on a wooden shelf against a plain green background.

Agendas for this week involve pinpointing individuals accountable for executing the off switch for the /random/ redirect feature, as well as organizing reports concerning the branded splits and analytics protocols related to referrals.

Google’s CDN recommendations warrant a review by those charged with CDN and firewall management, while the toggle for automated calls is governed by Business Profile configurations.

United Airlines’ regulations pertaining to agents are specified within legal agreements. Before embarking on subsequent changes, it is paramount to ascertain the entity responsible for each aspect within your organization.

Source link: Searchenginejournal.com.

Disclosure: This article is for general information only and is based on publicly available sources. We aim for accuracy but can't guarantee it. The views expressed are the author's and may not reflect those of the publication. Some content was created with help from AI and reviewed by a human for clarity and accuracy. We value transparency and encourage readers to verify important details. This article may include affiliate links. If you buy something through them, we may earn a small commission — at no extra cost to you. All information is carefully selected and reviewed to ensure it's helpful and trustworthy.

Reported By

Ranjana Banerjee

I’m Ranjana Banerjee, Creative Content Manager at RSWEBSOLS in Kolkata, India, with 10+ years of experience in blogging, SEO, digital marketing, and e-commerce. I create high-quality content and SEO strategies that boost traffic, improve rankings, and help businesses grow in competitive markets.
Share the Love
Related News Worth Reading