Website SEO Analyzer

How the Website SEO Analyzer works

Enter any URL and the analyzer fetches the page from the Cloudflare edge, parses the HTML, and runs five parallel checks simultaneously:

• Technical SEO — Parses meta title, description, canonical URL, Open Graph tags, Twitter Cards, JSON-LD structured data, viewport meta, charset, HTML5 doctype, favicon, HTML lang attribute, hreflang tags, noindex/nofollow directives, meta refresh detection, and HTTP→HTTPS redirect behavior. Also fetches robots.txt and sitemap.xml.
• Content SEO — Extracts visible text to count words, paragraphs, and sentences. Analyzes heading hierarchy, title keyword presence in H1 and body content, top keyword frequency, internal and external link counts, image alt text coverage, and placeholder text detection.
• Performance — Measures server response time from the Cloudflare edge (not real-user Core Web Vitals), HTML page size, Gzip/Brotli compression, Cache-Control headers, HTTP version detection, render-blocking script count, and samples up to 8 CSS and 8 JS assets for size totals.
• Mobile — Checks viewport meta configuration, CSS media query usage in inline styles and linked stylesheets, and Apple touch icon presence.
• AI Readiness — Checks for FAQPage JSON-LD schema, Organization schema, llms.txt presence, and content structure heuristics (clear H1, multiple H2+ headings, substantial word count, list usage) that help AI systems understand and cite your content.

The overall score uses a weighted model: Technical SEO (35%), Content SEO (25%), Performance (20%), Mobile (10%), AI Readiness (10%). Each category is scored independently on a 0–100 scale.

Who should use the Website SEO Analyzer

• IT admins and MSPs — Check client websites for technical SEO issues as part of a site health review. Use the Copy Summary function to send a plain-text report to clients or paste into a ticket.
• Developers — Verify that newly launched pages or content changes don't introduce SEO regressions. Check canonical URLs, structured data validity, and viewport configuration before and after deployments.
• Content and marketing teams — Quickly audit landing pages and blog posts for on-page SEO completeness before publishing. Check that meta descriptions, OG images, and heading structures are properly configured.
• Small business owners — Run a technical SEO check without needing a paid subscription to a dedicated SEO platform. Get actionable findings with clear explanations and effort estimates.

What is SEO and why does it matter?

SEO (Search Engine Optimization) is the practice of improving a website so that it ranks higher in organic (unpaid) search results on Google, Bing, and other search engines. When someone searches for a product, service, or answer, search engines return a ranked list of pages they believe are most relevant and authoritative. SEO is the discipline of making your pages the ones that appear at the top.

SEO matters because organic search is one of the highest-converting traffic channels for most businesses. A page ranking on the first page of Google for a relevant query receives dramatically more traffic than one on the second page. Unlike paid advertising, organic rankings provide compounding returns: a well-optimized page continues to generate traffic months and years after it was published, without ongoing spend.

SEO is not a single technique but a collection of disciplines: technical SEO (crawlability and site infrastructure), on-page SEO (content and HTML elements), and off-page SEO (backlinks and external signals). This tool focuses on the first two — the parts you can directly measure and control.

How search engines work

Search engines operate in three phases: crawling, indexing, and ranking.

• Crawling — Automated bots (Googlebot, Bingbot) follow hyperlinks from page to page, fetching each URL's HTML content. They respect your robots.txt file, which lists pages they are not allowed to fetch. Your XML sitemap supplements crawling by listing pages that may not be easily discovered through links.
• Indexing — After fetching a page, the search engine processes and stores it in a massive database (the index). This includes parsing the HTML, extracting content, analyzing structured data, and detecting signals like canonical URLs and noindex directives. Pages with a noindex directive are excluded from the index regardless of their quality.
• Ranking — When a user searches, the engine retrieves relevant pages from the index and ranks them using hundreds of signals: content relevance, page quality, backlinks, user experience signals (Core Web Vitals), mobile-friendliness, HTTPS, and more. This tool checks many of the on-page and technical signals that influence ranking.

Technical SEO vs on-page SEO

These two disciplines are often conflated but address different problems.

Technical SEO ensures search engines can find, access, and understand your pages. It asks: Can the crawler reach this page? Is it blocked by robots.txt or a noindex directive? Does it load fast enough? Is it mobile-friendly? Does it have a canonical URL to prevent duplicate content issues? Is it served over HTTPS? Does it have structured data that helps search engines understand the content type? Technical SEO problems are often binary — they either block a page entirely or they don't — and fixing them frequently produces immediate ranking improvements.

On-page SEO ensures the content of each page matches what users are searching for and signals relevance to search engines. It asks: Does the meta title contain the primary keyword? Does the H1 accurately describe the page topic? Is the content comprehensive enough to satisfy the user's intent? Are there internal links to related pages? Do images have alt text? On-page SEO is more iterative — improvements compound over time as content is refined and expanded.

Both are required for good rankings. A technically perfect site with thin, irrelevant content will not rank. Excellent content on a technically broken site may not be indexed at all. This tool measures both.

Structured data and rich results

Structured data is machine-readable markup embedded in HTML that tells search engines exactly what type of content a page contains — an article, a recipe, a product, a FAQ, an event. The most widely used format is JSON-LD, a JavaScript block in the <head> that uses Schema.org vocabulary.

Google uses structured data to generate rich results in search: FAQ accordions that expand directly in the search result, star ratings and review counts on product pages, recipe cards with cooking times and calorie counts, breadcrumb trails below the page title, event dates and ticket links. Rich results have significantly higher click-through rates than standard blue links — making structured data one of the highest-leverage improvements available to most sites.

The most impactful schema types for content sites:

• FAQPage — Generates accordion FAQ rich results. Also one of the most reliable ways to get content surfaced in Google AI Overviews and cited by AI search tools.
• Organization — Helps establish brand identity: name, logo, contact information, and social profiles. Appears in knowledge panels and is used by AI systems for brand disambiguation.
• BreadcrumbList — Displays breadcrumb navigation below the title in search results. Helps users understand site structure at a glance.
• WebSite — Enables the Google Sitelinks Search Box that appears below the homepage result for well-known sites.

Validate your structured data with Google's Rich Results Test before publishing. This tool checks for FAQPage, Organization, BreadcrumbList, and WebSite schemas in the AI Readiness and Technical SEO sections.

Core Web Vitals and performance

Google uses Core Web Vitals — a set of user experience metrics — as ranking signals. The three current metrics are:

• Largest Contentful Paint (LCP) — How long until the largest visible element (hero image, heading) is rendered. Good: under 2.5 seconds. Poor: over 4 seconds. Improve with faster servers, CDNs, and image optimization.
• Interaction to Next Paint (INP) — How quickly the page responds to user interactions (clicks, taps, key presses). Good: under 200ms. Improve by reducing JavaScript execution time and removing render-blocking scripts.
• Cumulative Layout Shift (CLS) — How much content unexpectedly shifts while loading. Good: under 0.1. Caused by images without dimensions, ads loading dynamically, or web fonts swapping.

This tool measures TTFB from the Cloudflare edge (a proxy for server response speed) and checks for render-blocking scripts, HTML size, and compression — all of which directly affect Core Web Vitals. For true CWV measurements, use Google Search Console (field data from real users) or PageSpeed Insights (lab data from a simulated browser).

AI readiness and llms.txt

AI-powered search is changing how users find information. Google AI Overviews, Perplexity, ChatGPT Search, and similar tools now answer queries directly — often citing and quoting from web pages. Whether your content gets cited depends heavily on whether AI systems can reliably extract, understand, and trust it.

The most important factors for AI readiness are the same as for traditional SEO — well-structured content, clear headings, complete structured data — plus some emerging considerations:

• FAQ schema — FAQPage JSON-LD is one of the most reliable ways to get specific answers surfaced by AI Overviews. AI systems parse structured Q&A data and prefer it over unstructured prose for direct answers.
• Organization schema — Helps AI systems correctly identify and attribute your brand. Prevents confusion between similarly named organizations.
• llms.txt — An emerging convention (similar to robots.txt) that describes a site's structure and key pages for AI crawlers. Placed at /llms.txt. Not yet an official standard, but being adopted by AI platforms for improved accuracy. Creating one is a low-effort early-adopter advantage.
• Content clarity — Well-structured content with clear H1 and H2 headings, short paragraphs, and list formatting is easier for AI systems to parse, summarize, and cite than dense, unstructured prose.

Common SEO mistakes and how to avoid them

• Missing or duplicate meta titles — Every page needs a unique title. Duplicate titles prevent search engines from understanding which page to rank for a given query. Keep titles under 60 characters and include the primary keyword near the start.
• Multiple H1 headings — One H1 per page signals the primary topic. Multiple H1s dilute the signal and can confuse crawlers.
• Missing canonical tags — Without canonicals, the same content accessible via multiple URLs (http vs https, www vs non-www, trailing slash vs none) may cause duplicate content issues. Always declare a canonical URL.
• Images without alt text — Alt text is required for accessibility (screen readers) and contributes to image search rankings. Every non-decorative image should have a descriptive alt attribute.
• Uncompressed assets — Serving HTML, CSS, and JavaScript without Gzip or Brotli compression wastes bandwidth and slows page load. Compression is typically a one-line configuration change and reduces file sizes by 60–80%.
• Thin content — Pages with fewer than 300 words are often considered low-quality. Search engines prefer pages that comprehensively cover a topic. Add genuine value — not filler — to thin pages.
• No sitemap — Without a sitemap, search engines rely entirely on links to discover your pages. A sitemap guarantees visibility and accelerates indexing, especially for newer sites.

Technical SEO checklist

Use this checklist to verify the most important technical SEO elements on any page. This tool checks all of these automatically.

• ✓ Page served over HTTPS
• ✓ HTTP redirects to HTTPS with a 301 redirect
• ✓ Unique meta title, 50–60 characters, includes primary keyword
• ✓ Meta description, 120–160 characters, compelling and keyword-relevant
• ✓ Exactly one H1 heading per page
• ✓ Heading hierarchy is sequential (H1 → H2 → H3, no skipped levels)
• ✓ Canonical URL declared and consistent with final URL after redirects
• ✓ robots.txt present and not blocking crawlers
• ✓ sitemap.xml present and submitted to Google Search Console
• ✓ Open Graph tags (og:title, og:description, og:image, og:url, og:type)
• ✓ JSON-LD structured data (at minimum WebSite and Organization on homepage)
• ✓ Viewport meta tag: width=device-width, initial-scale=1
• ✓ HTML lang attribute on <html> element
• ✓ Favicon present (link rel="icon")
• ✓ Gzip or Brotli compression enabled
• ✓ Cache-Control headers configured
• ✓ No render-blocking scripts in <head> (use defer or async)
• ✓ All images have alt text
• ✓ No noindex on public pages
• ✓ No placeholder text (Lorem Ipsum, "Coming Soon")
• ✓ Word count > 600 words for informational pages
• ✓ At least 2–3 internal links to related pages

Free vs paid SEO tools — what you actually need

The SEO industry is dominated by premium platforms charging hundreds of dollars per month. Understanding what each category of tool provides — and where free tools are genuinely sufficient — helps you avoid overspending on capabilities you don't need yet.

What free tools cover well

• Technical SEO auditing — This tool, Google Search Console, Screaming Frog (free tier up to 500 URLs), and browser DevTools give you complete visibility into on-page and technical issues: missing meta tags, broken canonical URLs, missing structured data, slow server responses, and render-blocking scripts. No subscription required.
• Performance measurement — Google PageSpeed Insights and Google Search Console's Core Web Vitals report provide field data from real users at no cost. These are the same metrics Google uses for ranking decisions.
• Index coverage and crawl errors — Google Search Console shows exactly which pages are indexed, which are excluded, and why. It surfaces manual actions, crawl errors, and mobile usability issues in real time.
• Structured data validation — Google's Rich Results Test and Schema.org Validator are free and authoritative. They show exactly which schema types are detected and whether they are eligible for rich results.
• Security and header checks — Tools like the Website Security Scanner on this site check TLS certificates, security headers, HSTS, and CSP configuration — all at no cost.

What paid tools add

• Backlink databases — Ahrefs, Semrush, and Moz maintain continuously updated indexes of billions of backlinks. This data requires internet-scale crawling that no free tool can replicate. If your strategy depends on link building or competitor backlink analysis, a paid tool is necessary.
• Keyword research at scale — Search volume data, keyword difficulty scores, and SERP analysis require proprietary data that paid platforms license from clickstream data providers. Free tools like Google's Keyword Planner provide ranges, not precise volumes.
• Rank tracking — Monitoring keyword rankings over time across locations and devices requires daily SERP checks that exceed what free tools offer. Google Search Console shows average position but not daily rank movement.
• Large-scale site audits — Screaming Frog's free tier caps at 500 URLs. For sites with thousands of pages, paid crawlers like Screaming Frog Pro, Sitebulb, or Semrush Site Audit handle the volume.
• Competitive intelligence — Understanding what keywords competitors rank for, which pages drive their traffic, and which sites link to them requires proprietary index data that only paid platforms provide.

The right approach by stage

For most small to mid-sized sites, the combination of Google Search Console + this tool + PageSpeed Insights covers the vast majority of actionable technical SEO work. Start there. Fix all technical issues, ensure your on-page fundamentals are solid, and build content quality before spending on premium platforms. The returns from fixing a missing meta description or enabling compression are immediate and measurable. The returns from a backlink database only matter once your technical foundation is correct and your content is genuinely competitive.

Related tools