Pillar 2 of 8 · The UltimateSEO Framework

Technical eligibility

Before any search engine or AI system can judge the quality of a page, it must be able to fetch, render, canonicalise and index the URL reliably. This pillar covers HTTP status and main content, robots.txt versus noindex, crawlable navigation, WAF and CDN behaviour towards real crawlers, canonical signals, sitemaps and IndexNow, language and region versions, JavaScript rendering, mobile parity, Core Web Vitals, HTTPS and the crawler policies of Google, OpenAI, Anthropic, Perplexity and Bing. Most of these controls can be evidenced automatically from a crawl, which makes this the pillar where an instant scan gives the most definite answers.

Controls: 16
P0 gate controls: 9
Hard gates: 5

Branches and controls

Every control in this pillar, with priority, evidence base and how it is checked

Automated the scan can produce pass or fail evidence on its own. Partly automated the crawl gives a signal, a person decides. Needs your evidence Search Console, logs, business facts or reviews are required; the state stays UNKNOWN until you supply them.

T.A Crawl, HTTP and indexable content 4

ID	Control	Priority	Evidence base	Checked by
T-01	Public URLs must be technically reachable and carry real main content Hard gate	P0	Official	Automated
T-02	robots.txt and noindex must be used for different purposes Hard gate	P0	Official	Automated
T-06	Critical navigation must use real crawlable links	P1	Official	Automated
T-11	WAF and CDN must be configured so they do not block real crawlers	P0	Strong practice	Partly automated

T.B Canonical, discovery and URL management 3

ID	Control	Priority	Evidence base	Checked by
T-03	Canonical signals must converge on a single target Hard gate	P0	Official	Automated
T-04	Sitemap and IndexNow must stay in sync with real URL status	P1	OfficialStrong practice	Automated
T-10	Language and region versions must be managed consistently	P1	Strong practice	Automated

T.C Render, mobile, performance and security 4

ID	Control	Priority	Evidence base	Checked by
T-05	JavaScript rendering must be reliable Hard gate	P0	Official	Partly automated
T-07	Mobile-first parity must be maintained	P0	Official	Automated
T-08	Core Web Vitals must be managed with field data	P1	Official	Partly automated
T-09	HTTPS must be the baseline security standard Hard gate	P0	OfficialStrong practice	Automated

T.D Platform crawlers and AI eligibility 5

ID	Control	Priority	Evidence base	Checked by
T-12	Google generative Search eligibility must be built on core Search eligibility	P0	Official	Automated
T-13	OpenAI search, training and user-directed crawler roles must be managed separately	P0	Official	Automated
T-14	Anthropic crawler roles must be managed separately	P1	Official	Automated
T-15	PerplexityBot access must be managed deliberately	P1	Official	Automated
T-16	Bing crawl, indexing and AI telemetry must be set up together	P1	Official	Automated

Back to the framework hub · How the publish gate uses these controls