Technical SEO, Checked the Way Search Engines See it.
Find what stops a page being crawled, rendered or understood. Check one URL for twelve readings with the evidence behind each, then open the tool that explains the fix. 21 free tools, no account.
- ResponseHTTP 20063 ms · 202 KB
- IndexableYesNo noindex directive
- GooglebotAllowedNo rule matches
- AI crawlers35 of 35None blocked by robots.txt
- CanonicalSelfhttps://www.apple.com/uk/
- hreflang137 versionsNo x-default
- ViewportResponsivewidth=device-width, initial-scale=1, viewport-fit=cover
- Structured Data5 typesContactPoint, Organization, SearchAction, WebPage…
- Title22 charsApple (United Kingdom)
- Social cardCompleteTitle, description and image
- Sitemap5 in robots.txthttps://www.apple.com/shop/sitemap.xml +4
- llms.txtNoneNo /llms.txt (optional)
Every Tool, by What it Checks.
Pick the question you have. Each tool answers it on its own page, with the evidence and what to do next.
Crawling
What crawlers may fetch, what they find and where links break.
- robots.txt TesterIs a URL blocked, and by which rule?
- AI Bot Access TesterWhich AI crawlers can read your pages.
- .htaccess TesterTest Apache rewrites and redirects.
- Sitemap GeneratorCrawl a site into an XML sitemap.
- Broken Link CheckerFind every broken link and image.
- llms.txt ToolValidate or generate an llms.txt.
- RSS Feed ParserRead and validate any feed.
Rendering
What a crawler's browser builds from your HTML and JavaScript.
Mobile SEO
Google indexes the phone version. Make sure it holds up.
International SEO
The right language and country version for every visitor.
Structured Data
Markup that makes a page eligible for rich results.
Search Appearance
How your pages look in Google and when they're shared.
Local SEO
Results from any place, and reviews for your business.
What Crawlers Get, Not What Your Browser Shows.
Crawler Rules, to the Letter
robots.txt is matched the way RFC 9309 and Google's documentation describe, for Googlebot, Bingbot and 35 AI crawlers.
A Real Browser
Pages are rendered in headless Chromium, the engine Googlebot renders with, sending Googlebot's user agent, so you see what JavaScript adds, hides or breaks.
Nothing to Sign Up for
No account, and results aren't saved. Every tool is also a JSON endpoint, so you can script the same checks.
Google Ships Updates. Here They Are.
The latest confirmed ranking updates, live from Google's Search Status Dashboard.
- Nov 10, 2026Rolling outNovember 2026 core updateReleased the November 2026 core update, which applies globally and to all languages. The rollout may take up to 2 weeks to complete.In progress
- Sep 24, 2026September 2026 spam updateReleased the September 2026 spam update, which applies globally and to all languages. The rollout may take up to two weeks to complete.Completed Oct 8, 2026
- Aug 18, 2026August 2026 spam updateReleased the August 2026 spam update, which applies globally and to all languages. The rollout may take a few days to complete.Completed Aug 21, 2026
- Jun 24, 2026June 2026 spam updateReleased the June 2026 spam update, which applies globally and to all languages. The rollout may take a few days to complete.Completed Jun 26, 2026
Questions, Answered.
The Guides go deeper on robots.txt, hreflang, canonicals and llms.txt.
Yes. Every tool works without an account. Knowledge Graph and Place ID lookups use Google APIs and need a key on the server.
Pages are fetched by this server, not your browser. Sites that block data-centre traffic or verify crawlers by IP can answer differently than they would to the real Googlebot; the tools say so when a response looks like a refusal.
No. Each test runs on demand and the result goes straight back to your browser. Nothing is saved to a database; the host keeps its standard short-lived request logs.
Close, not identical. robots.txt matching follows RFC 9309 and Google's documentation, pages render in Chromium with Googlebot's user agent, and mobile checks use Googlebot Smartphone at 412 px. The requests come from our servers, not Google's, so a site that treats Google's IP addresses differently can answer differently. Ranking signals are out of scope.
Yes. POST a URL to /api/<tool> and you get the same result the page shows, as JSON. The API docs list every endpoint.
Start with One URL.
Twelve readings in about a second. No card, no account.