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 330-check register puts 100 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 330-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.
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 330 audit checks belong to technical SEO foundations?
130 checks in the Technical Foundations pillar of the 330-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 100 checks of the 330-check AEO audit 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.