Search DevTools

Jump to any tool or page

SEO Website Analyzer

Deep dive into your website's performance, SEO, and accessibility. Get actionable insights to improve your score.

Website

Report

Analyze a URL to see performance, SEO, and accessibility results here.

Developer Utilities

About SEO Website Analyzer

Fetch a page and inspect the signals crawlers actually consume — title and meta description, canonical, robots directives, heading structure, Open Graph tags, structured data and hreflang. The analysis reads the raw HTML response, which is the useful vantage point: Googlebot's first pass sees exactly this, and anything injected after hydration only reaches the index if and when rendering is queued.

Related Developer Utilities tools

Token CounterZod GeneratorBase64 Encoder/DecoderSecret ScannerHash Generator

Frequently asked questions

Do title and meta description lengths have hard limits?
No — the limit is pixel width in the SERP, not characters. Google truncates titles at roughly 600 CSS pixels, which is about 50 to 60 characters in a typical mix, and wide letters exhaust that budget faster than narrow ones. Descriptions get around 155 to 160 characters on desktop and less on mobile. Neither is a ranking factor directly, and Google rewrites titles it judges unhelpful in a substantial share of cases, usually preferring the h1 or the site name.
What is the difference between noindex, robots.txt disallow and a canonical?
They act at different stages and are frequently combined incorrectly. robots.txt blocks crawling, so a disallowed URL can still be indexed from external links — with no snippet, because the crawler was never allowed to read the page. noindex allows crawling and forbids indexing, which means a URL blocked in robots.txt can never have its noindex seen. A canonical is only a hint about which duplicate to consolidate; Google may pick a different URL if the signals disagree.
Does client-side rendering hurt indexing?
It delays and complicates it. Google crawls the raw HTML first, then queues the page for rendering with a headless Chromium — a second pass that can lag from hours to weeks and is subject to a resource budget. Content, links and meta tags present only after hydration are invisible until then, and other crawlers, including most social scrapers and several search engines, never render at all. Server-side rendering or static generation of the critical markup avoids the whole class of problem.
How much does heading structure actually matter?
Less than folklore suggests, more than nothing. Multiple h1 elements are valid HTML5 and Google has stated they are not a problem; the real value of a heading hierarchy is accessibility, since screen reader users navigate by heading level, and skipping from h2 to h4 breaks that. Headings also give Google material for featured snippets and jump-to links. What genuinely harms you is using headings for visual sizing rather than structure, so the outline no longer describes the content.
Which structured data is worth adding, and what breaks it?
Only types with a documented rich result do anything visible: Article, Product with offers and reviews, FAQPage, HowTo, BreadcrumbList, Organization, LocalBusiness and Event. JSON-LD in a script tag is Google's stated preference. The common failures are marking up content not present on the page, which is a policy violation and can trigger manual action; missing required properties, which silently disqualifies the whole item; and injecting JSON-LD via a tag manager, which then depends on the rendering pass to be seen.