SEO, AEO, and GEO guides for a world where AI answers search queries.
Classic SEO still matters. But AI search engines — ChatGPT, Perplexity, Google AI Overviews — use different ranking signals. These guides cover both surfaces and how they interact.
Latest industry news
What changed, as it happens.
Tracked daily from primary sources. The items below are what we're watching for clients right now.
Google's Gary Illyes said Google's crawlers send HTTP HEAD, OPTIONS, PUT, PATCH and DELETE requests in addition to GET and POST. Those five account for under 1.5% of the total number of requests Google's crawlers send, and Illyes attributed them to JavaScript.Source: Search Engine Roundtable →
Our take: Under 1.5% of requests is a rounding error, and for most stores this is trivia. Blocking PUT, PATCH and DELETE as write methods is ordinary security practice on a hardened origin, and Illyes has now put a Google crawler inside that rule. The methods are tied to JavaScript, so the cost of a block lands on rendering.
Google's August Small Business Bulletin says Business Profile in Gemini is now available globally on desktop and mobile, and that tagging @Google Business Profile works for accounts managing more than one profile, lifting a single-profile limit that had been in place since the June 10 launch. Gemini drafts updates to hours, services, photos and other listing details, and approved changes go out through the official Business Profile APIs under the same verification standards applied to manual edits. Nothing publishes without owner review, and the integration is free on all Gemini accounts, though it still works only with personal Gmail accounts and not with Google Workspace.Source: PPC Land →
Our take: Multi-location support and personal-Gmail-only are hard to hold at the same time. A business running several profiles is a business with a Workspace domain, so this lands for the accounts least likely to have it. The window where it fits is narrow: listings set up years ago on someone's personal Gmail and never migrated. Owner review gates every edit either way, so what Gemini produces is a draft.
A site owner posting in r/TechSEO reported that switching on Cloudflare's "AI Training = Block" control returned HTTP 403 responses to both Googlebot and Bingbot, including on the sitemap, and that the problem cleared when the block was switched off. Cloudflare's own dashboard classifies Googlebot and Bingbot as "Search + Training" bots. Google's John Mueller asked the poster to get in touch so he could look into it. Another commenter raised spoofed bots as an alternative explanation, which the poster rejected on the basis that Cloudflare's dashboard was reporting verified crawler activity. The report is anecdotal, and it is not established whether it reflects a configuration mistake or announced behavior arriving early. Cloudflare has separately published the policy behind it: from 15 September 2026 it sorts crawlers into Search, Agent and Training, and states that multi-purpose crawlers combining Search with Training will be blocked according to all of their behaviors. It names Googlebot, Applebot and BingBot as crawlers that will be blocked for customers who have chosen to block Training, because the defaults are enforced by the most restrictive applicable rule. Site owners can record an override in Cloudflare's Security settings at any point before 15 September, confirming they want no change applied to Training crawlers that also crawl for Search.Source: Search Engine Journal →
Our take: Blocking AI training is the least controversial thing a store owner can do in a Cloudflare dashboard, which is what makes this one expensive. Googlebot fetches for Search and for Google's AI products through the same crawler, so a control that reads as keeping your catalog out of model training is also the control deciding whether your products stay indexed. The override is one setting and it takes a minute. Nothing about the training toggle tells you that you need it.
Aleyda Solis analyzed the top 10 cited source domains for 15 leading brands in each of three verticals, SaaS, ecommerce and finance, across Google AI Mode, Gemini and ChatGPT using Semrush Enterprise data, then classified every cited domain by who owns it. In all three verticals the brand's own website was a minority of the cited mix. SaaS came in at 82.3% external and 17.7% owned, finance at 79.4% external and 20.6% owned, and ecommerce at 69.6% external and 30.4% owned. Solis frames the owned site as an "on-page corroboration base": the canonical statement of product, policy and documentation facts that social, community, publisher, review, marketplace and competitor sources then validate, compare or challenge. Her recommendations include treating third-party citations as core rather than optional, identifying which specific sites influence a target prompt before choosing PR or social targets, and connecting cited evidence back to a commercial destination.Source: Aleyda Solis →
Our take: Ecommerce is the least dependent of the three verticals on other people's pages, which is the reverse of how this study gets quoted. A third of the mix is still the minority share, so the schema and content work every store already does buys that third and cannot buy the rest. Where the other two thirds sit varies by prompt, and a review site that dominates one query can be absent from the next one over. Nobody can name your external targets from a vertical average.
Google updated its crawl-budget documentation with two substantial additions. The first is a recommendation to support HTTP caching, worded as: "Support 304 (Not Modified) HTTP status codes. If a page hasn't changed since Google last crawled it, returning a 304 code tells Google to reuse the cached version, saving your server bandwidth and resources." The second is a clarification that the crawl capacity limit is shared across all crawlers, so high demand from one crawler such as Googlebot-Image reduces the capacity available to the others. The document scopes its guidance to enterprise sites above one million pages and medium sites above ten thousand pages that change rapidly. Search Engine Journal reports these were the only substantial additions, with minor clarifications elsewhere in the page.Source: Search Engine Journal →
Our take: Image crawling and page crawling draw on the same pool, which means an oversized image set is competing with your product pages for the same requests. The 304 half is a server response rather than a setting in your store admin, so on hosted BigCommerce or Shopify the question is what your platform and CDN already return for a page that has not changed. For most stores this turns out to be somebody else's checkbox.
Deep dives, explainers, and the questions clients ask most.
New · June 2026
Measuring AI Search Visibility
Search Console's new generative-AI reports, Merchant Center's AI report, and Preferred Sources — the first native data on how often AI surfaces show you, and what to do with it.
Generative Engine Optimization explained. What AI search engines rank on, how it differs from classic SEO, and the 6 signals that matter most for ecommerce stores.
Product, BreadcrumbList, FAQ, and Article schema in priority order — what AI agents read first, where FAQ markup still counts after the 2026 deprecation, and the mismatches that cost eligibility.
What BigCommerce does with filter URLs and canonicals by default, the robots.txt parameter rules that stop crawl waste, and how to promote money filter combos to indexable pages.
GPTBot, ClaudeBot, PerplexityBot, Googlebot-Extended — which AI crawlers exist, what they do with your content, and how to control access without accidentally blocking yourself from AI search results.
The honest guide: what llms.txt does and doesn't do in 2026, who actually reads it, what Google says, why we ship one anyway — and a copy-paste structure for a store.
The most common SEO mistakes made during platform migrations — and the before/during/after checklist that avoids ranking drops. URL mapping, redirect chains, and the 90-day watch.