<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technical Seo on AECITED — AI visibility: analyzed and fixed monthly</title><link>https://aecited.com/tags/technical-seo/</link><description>Recent content in Technical Seo on AECITED — AI visibility: analyzed and fixed monthly</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 29 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aecited.com/tags/technical-seo/index.xml" rel="self" type="application/rss+xml"/><item><title>Technical SEO Hygiene Checklist: Which 'Limits' Are Google Rules?</title><link>https://aecited.com/posts/seo-technical-hygiene-checklist/</link><pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate><guid>https://aecited.com/posts/seo-technical-hygiene-checklist/</guid><description>&lt;p>&lt;strong>The technical SEO hygiene baseline in 2026 is a two-layer list: first fix discovery and indexing (robots.txt, sitemap, internal links, redirect hygiene), then fix presentation (title, meta description, image alt text, heading structure, URL structure, anchor text) — and know that most of the famous numbers in that list (60-character titles, 160-character descriptions, images under 200 KB, 3–8-word anchors, redirect chains under 2) are conventions, not Google rules.&lt;/strong> The asks Google actually documents are qualitative: descriptive, relevant, human-readable, &amp;ldquo;shorter is better.&amp;rdquo; Follow the numbers as display heuristics, because they are calibrated to how results render — but do not believe that a broken checklist item is what is holding you back, unless the item is one of the few Google actually owns. That distinction is what this post exists for.&lt;/p></description></item><item><title>What Is Keyword Cannibalization (And How to Fix It)</title><link>https://aecited.com/posts/keyword-cannibalization/</link><pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate><guid>https://aecited.com/posts/keyword-cannibalization/</guid><description>&lt;p>&lt;strong>Keyword cannibalization is when two or more pages on your site target the same search intent, and Google has to pick one representative page to evaluate for that query — so the pages split signals between them instead of reinforcing each other.&lt;/strong> It is practitioner terminology; Google never uses the phrase &amp;ldquo;keyword cannibalization&amp;rdquo; in its documentation. But the mechanics it describes are fully documented, under different names: &lt;a href="https://developers.google.com/search/docs/crawling-indexing/canonicalization">canonicalization&lt;/a> (how Google selects the representative URL for a piece of content) and &lt;a href="https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls">duplicate URL handling&lt;/a> (how you tell it which page to keep). The fix is a short procedure — pick one page, consolidate the other, consolidate your internal links, then watch Search Console — and the rest of this post is what that procedure looks like, step by step.&lt;/p></description></item><item><title>Cloudflare Disallow AI Training: audit after the Sept 15 migration</title><link>https://aecited.com/posts/cloudflare-disallow-ai-training/</link><pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate><guid>https://aecited.com/posts/cloudflare-disallow-ai-training/</guid><description>&lt;p>On September 15, 2026, Cloudflare quietly rebuilt one of the most consequential settings a website owner will ever toggle. The old &amp;ldquo;Block AI Bots&amp;rdquo; switch — a single yes/no that blocked some AI crawlers while leaving mixed-use ones alone — was deprecated and replaced with three separate controls: &lt;strong>Search, Training, and Agent&lt;/strong>, plus a new &lt;strong>Disallow AI Training&lt;/strong> setting that publishes a no-training preference to &lt;a href="https://aecited.com/posts/aeo-glossary/">robots.txt&lt;/a> while keeping you indexed for search. The catch that most write-ups miss: your old settings were &lt;strong>migrated automatically under you&lt;/strong>, and the new &amp;ldquo;Block&amp;rdquo; now means something different — it can stop Googlebot and Bingbot, search included. This post covers what changed, the verified migration table, the decision it forces on a B2B SaaS site, and the ten-minute audit you should run whether or not you care about AI training.&lt;/p></description></item><item><title>llms.txt in 2026: what the v2 spec requires, in 20 minutes</title><link>https://aecited.com/posts/llms-txt-v2-audit/</link><pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate><guid>https://aecited.com/posts/llms-txt-v2-audit/</guid><description>&lt;p>Ask any search engine for &amp;ldquo;&lt;a href="https://aecited.com/posts/aeo-glossary/">llms.txt&lt;/a> best practices&amp;rdquo; in October 2026 and you get a wall of third-party guides. The spec itself — llmstxt.org, v2, modified August 10, 2026 — sits further down the results. That&amp;rsquo;s a gap, because the guides are mostly written to v1 habits, and v2 changed several of the things the guides now treat as requirements. This audit goes back to the spec and checks only what it actually says. If you would rather start with a broader pass, &lt;a href="https://aecited.com/posts/first-20-minutes-aeo-audit/">your first 20 minutes of AEO&lt;/a> covers the manual audit end to end.&lt;/p></description></item></channel></rss>