Technical foundations are the checks that decide whether a page is even eligible to be ranked or cited: it must be reachable, return 200 over HTTPS, be indexable, render its content in the raw HTML, declare one canonical URL, sit in the XML sitemap and pass Core Web Vitals. Laurelin's 387-check register puts 138 of its checks in this pillar because no amount of content or authority work matters for a page a crawler cannot fetch. This hub links the technical audit service, the pillar-one audit checks, the IndexNow submitter and the graph tooling that maps a site's crawl structure.
None of the visibility work matters if a machine cannot crawl, render and index the page in the first place. This is the foundation layer, codified as a 387-point technical audit across four pillars, every check cross-referenced to a primary source. Second-largest cluster by demand and the strongest bottom-of-funnel intent.
Which technical SEO foundations services does Laurelin offer?
Which free tools and lab builds cover technical SEO foundations?
IndexNow Submitter
A free URL submitter built on the IndexNow protocol: verify your site once with a key file, then push new and updated URLs to Bing, Yandex, Seznam and Naver in a single call. It also checks the sitemap Google actually reads and gives an honest manual workflow for Brave, whose form cannot legitimately be automated.
AEO Graph View
An Obsidian-style visual node graph of a website where each node is a page and each edge an internal link, with toggleable data layers, rankings, backlinks, status codes, on-page scores, analytics, technical issues and proposed information architecture, so structure and performance are visible at a glance.
Internal Linking Intelligence
A feature that auto-generates internal link suggestions from an uploaded site crawl, producing contextually relevant links from real structure rather than generic keyword matches, and flagging the missed opportunity when no crawl is provided. Suggestions are scored on topical proximity and the target page's need for links, so the tool strengthens hub pages rather than scattering links evenly.
Which Google search systems bear on technical SEO foundations?
Page experience system
Page experience is Google's label for how users perceive interacting with a page: Core Web Vitals, secure delivery, mobile display, ads and interstitials. Google confirms that its core ranking systems look to reward good page experience, but since 2023 it has said this was never a separate ranking system or a single combined signal, and since 2024 its documentation says only Core Web Vitals are used directly in ranking. For a site, page experience is a tie-breaker when relevance is close, measured on real-user field data.
Page speed system
The page speed system was Google's use of page load speed as a ranking signal: first for desktop searches in 2010, then for mobile searches through the July 2018 Speed Update. Google confirmed both, and described both as small, affecting only the slowest pages or a small share of queries. It was removed from Google's ranking systems guide in April 2023. Speed still matters through Core Web Vitals, which Google says its ranking systems use, so the practical job is fixing the slowest templates on mobile field data.
Mobile-friendly ranking system
The mobile-friendly ranking system was Google's use of mobile-friendliness as a ranking signal for mobile searches, expanded worldwide from 21 April 2015 and nicknamed Mobilegeddon by the industry. Google confirmed it. In April 2023 it was removed from the ranking systems guide, and Google retired the Mobile-Friendly Test and Mobile Usability report from December 2023. Google now says aspects of page experience other than Core Web Vitals do not directly help rankings, so mobile display is a user requirement first.
Secure sites system (HTTPS)
The secure sites system was Google's use of HTTPS as a ranking signal, announced in August 2014 as a very lightweight signal affecting fewer than 1% of global queries. Google confirmed it and later listed HTTPS as a page experience signal. In April 2023 the secure sites system was removed from Google's ranking systems guide, and Google now says page experience aspects other than Core Web Vitals do not directly help rankings. HTTPS remains a baseline for users, browsers and clean site migrations rather than a ranking lever.
Mobile-first indexing
Mobile-first indexing means Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking. Google confirmed it, began experiments in 2016, declared the migration complete in October 2023 and stopped crawling the remaining sites with desktop Googlebot after 5 July 2024. It is infrastructure, not a ranking boost. For a site, anything missing from the mobile version (text, links, images, structured data, robots directives) is missing from Google's index.
Web Rendering Service (WRS)
The Web Rendering Service is the Googlebot component that runs a page's JavaScript in a headless, evergreen version of Chromium so Google can index the rendered HTML. Google confirms it by name in its JavaScript documentation and announced the evergreen Chromium change in May 2019. It is infrastructure, not a ranking system. For a site, it means content injected by JavaScript can be indexed, but only if rendering succeeds, resources are crawlable, and the WRS is not served stale cached scripts.
Caffeine
Caffeine is the web indexing system Google completed in June 2010. It replaced a layered, batch-refreshed index with one that updates continuously as pages are crawled, and Google said it delivered 50 percent fresher results. A Google paper presented at OSDI 2010 describes the Percolator system underneath it. Caffeine is infrastructure, not a ranking signal. For a site, it means new and changed pages can reach the index quickly, provided Google can discover and crawl them.
Deduplication systems
Deduplication systems are Google's confirmed ranking systems that stop near identical pages from filling the results. When several pages are very similar, Google shows the most relevant one, and since January 2020 a page shown as a featured snippet is not repeated on the first page. Canonicalisation is the related indexing step that picks one URL from a set of duplicates. For a site, duplicate URLs compete with each other and only one is likely to be shown, so consolidate them and signal a clear canonical.
What has Laurelin published on technical SEO foundations?
418 I'm a teapot: the HTTP status code that refuses to brew coffee, and why it will never be deleted
Where HTTP 418 came from (an April Fools RFC in 1998), how a fifteen-year-old saved it from deletion in 2017, why RFC 9110 now reserves it forever, the other status codes with a sense of humour, and why laurelinlabs.com/coffee refuses to brew.
I built a URL submitter for Google, Bing and Brave. Only one of them wanted it.
The honest state of URL submission in 2026: what Google actually accepts, why IndexNow is the only real API, what happened when we automated the Brave form, and the free tool that came out of it.
Which of the 387 audit checks belong to technical SEO foundations?
138 checks in the Technical Foundations pillar of the 387-check AEO audit, each cited to a primary source. The most consulted first.
- robots.txt missing entirely
- robots.txt returns 5xx
- robots.txt Disallow: / blocking whole site
- robots.txt blocks CSS/JS needed to render
- robots.txt blocks a directory with indexable content
- Sitemap not declared in robots.txt
- robots.txt over 500KB
- Conflicting Allow/Disallow rules
- Crawl-delay set unreasonably high
- Meta robots noindex on a page that should be indexed
- Meta robots nofollow suppressing internal links
- Meta robots nosnippet, kills AI-feature eligibility
- max-snippet:0 directive
- max-snippet set very low
- data-nosnippet wrapping primary content
- noarchive directive
- notranslate unintentionally set
- noimageindex blocking image visibility
- unavailable_after date in the past
- X-Robots-Tag noindex in HTTP header
- X-Robots-Tag nosnippet/none in header
- Meta robots and X-Robots-Tag conflict
- Duplicate meta robots with conflicting values
- Directive placed in <body> not <head>
Frequently asked questions about technical SEO foundations
What is a technical SEO foundations audit?
A systematic pass over crawlability, indexation, rendering, canonicalisation, site speed, HTTPS, sitemaps and URL structure, each check tied to a documented Google or W3C source. Laurelin runs it as the first 130 checks of the 387-check AEO audit, plus 8 checks tied to Google search systems, and reports every failing item with its severity, its evidence and the fix.
Do AI crawlers follow the same rules as Googlebot?
Largely. GPTBot, ClaudeBot, PerplexityBot and Google-Extended obey robots.txt, fetch the raw HTML and mostly do not execute JavaScript, so server-rendered content, clean status codes and open robots rules matter more for AI search than for Google, not less.