SEO Analyzer

The audit inspects the document title, meta description, canonical link, robots meta tag, language, character encoding, viewport, hreflang values, and other head metadata. It reports missing or questionable values and shows how the page may appear in Google and when shared through common social platforms.

Use a unique, descriptive title that matches the page's primary purpose. Write a useful meta description for the intended searcher, and make sure the canonical resolves to the preferred indexable URL. Canonical tags are hints for duplicate URL management, not substitutes for consistent internal links and redirects.

A clear heading hierarchy makes long content easier to scan and helps communicate its structure. The analyzer lists headings from H1 through H6, flags skipped levels, and checks whether the page uses a focused H1. It also counts words so thin or unexpectedly empty rendered output is easier to spot.

Image checks cover alt attributes, intrinsic dimensions, srcset, sizes, lazy loading, and responsive delivery. Link analysis separates internal and external URLs, reviews descriptive anchor text and crawlability, and checks reachable links for failures or redirect chains.

The tool fetches robots.txt, validates its basic structure, lists declared sitemaps, and shows whether selected crawler user agents are allowed. It also discovers an XML sitemap, reports fetch status and format, surfaces validation issues, counts URLs, and displays a sample of submitted locations.

Robots.txt controls crawling, not guaranteed indexing. A URL can still be known through links, and blocking a page can prevent a crawler from seeing a noindex directive on that page. Align robots rules, meta robots, HTTP headers, canonicals, status codes, and sitemap inclusion with the same indexing decision.

Indexability checks combine the page's HTTP response and crawler-facing directives to surface conflicts. Resolve failed status codes, unintended noindex values, blocked resources, and contradictory canonical signals before spending time on smaller content refinements.

The structured data section detects JSON-LD, microdata, and RDFa and summarizes schemas, errors, and warnings. Valid schema can help a search engine understand eligible entities and page features, but it does not guarantee a rich result. Keep markup consistent with visible content and the current documentation for the schema type.

Client-side applications may send a nearly empty HTML document and add meaningful text, headings, and links only after JavaScript runs. The analyzer compares raw and rendered word and heading counts to estimate JavaScript reliance. A large difference is not automatically an error, but it can make crawling, previews, accessibility, and failure recovery less predictable.

Server rendering or static generation can expose essential content and links earlier. After changing the rendering strategy, rerun the audit and inspect the source response, rendered page, canonical, and internal links. Pair the SEO review with the Core Web Vitals Checker because rendering architecture can affect both discovery and user experience.

The AI crawlability section reviews selected AI bot directives in robots.txt, meta robots and X-Robots-Tag signals, llms.txt availability, indexability, and no-JavaScript content. These checks help document the access rules your site publishes for different user agents.

Technical access does not guarantee that an AI service will crawl, include, cite, or rank a page. An llms.txt file is also not a replacement for useful HTML, clear internal linking, robots controls, XML sitemaps, or accurate structured data. Treat this section as one part of the broader crawlability audit.

Start with unsuccessful HTTP responses, unintended noindex directives, blocked pages, broken canonicals, and severe rendering failures. Next fix missing or duplicate titles, unclear headings, broken internal links, inaccessible image alternatives, and structured data errors. Warnings about lengths or counts require editorial judgment and should not be treated as universal ranking rules.

Audit representative templates as well as individual URLs. A problem in a shared product page, article, category, or landing-page template can affect many pages. After deployment, rerun the report, crawl the relevant URL set, and monitor search engine indexing and performance data for real outcomes.

Automated checks are best at finding observable technical conditions. They cannot judge whether content fully satisfies search intent, demonstrates original experience, earns trust, or deserves to outrank competing pages. A perfect score can coexist with weak content, and a strong page can contain a warning that is harmless in context.

Review each finding against the page's purpose. Make changes that improve clarity, accessibility, crawlability, and usefulness for people, then use search analytics and controlled testing to evaluate the result.