WEBSITE AUDIT REPORT
Example Domain
OVERALL SEO SCORE
Checks are based on public HTML and responses. Review the evidence and recommended actions below.
NEXT STEPS
Up to four findings, ordered by check weight.
Describe what this specific page offers and avoid reusing the same description across every page.
Use H1 for the main subject and H2/H3 for logical subsections, rather than selecting levels for visual size alone.
Match markup to visible content and validate it with a rich result testing tool. Eligibility does not guarantee display.
Link important pages with standard a href links and use text that describes the destination.
Review the observed values, context and actions for each check.
An illustration using the saved title and description. Actual results may differ.
No meta description was detected. A search engine may select a snippet from the page.
14 characters · tool reference range 10-70
The title identifies the page and its subject. The character range below is this tool’s heuristic, not a search engine limit.
Write a distinctive title, lead with the subject and avoid repeating keywords or the brand.
0 characters · tool reference range 70-160
The meta description summarizes a page. Search engines may show a different snippet for a query or device.
Describe what this specific page offers and avoid reusing the same description across every page.
Targethttps://example.com/
Response HTML <head> > meta[name=description]
Edit the head template’s description with this page’s service, audience and features. Avoid filler text.
<meta name="description" content="Summarize this page’s actual service and key information.">
A canonical link signals the preferred URL among similar pages. Its presence does not confirm which URL a search engine selects.
Check that the preferred URL works and agrees with HTTPS, internal links and sitemap URLs.
Targethttps://example.com/
Response HTML <head>
Add this to head if the analyzed URL is the actual canonical URL; otherwise substitute and verify the correct URL.
<link rel="canonical" href="https://example.com/">
This checks noindex and none directives in HTML and response headers. It does not query a search engine’s index.
Remove unintended noindex directives from public pages and check actual indexing with the search engine’s URL inspection tool.
Open Graph supplies title, description and image candidates for link previews. This check looks for those three properties.
Use page-specific sharing metadata and verify that the image URL is publicly accessible.
Targethttps://example.com/
Response HTML <head>
Review the sharing metadata and fill missing properties. Replace bracketed placeholders with actual values.
<meta property="og:title" content="[Page title]"> <meta property="og:description" content="[Page summary]"> <meta property="og:image" content="[Public image URL]">
Card metadata describes a sharing preview format. Detecting a tag does not verify the preview shown by a platform.
Review the card type, title, description and image together, allowing for platform caching.
Targethttps://example.com/
Response HTML <head>
Declare a card type in head and review the sharing image, title and description together.
<meta name="twitter:card" content="summary_large_image">
JSON-LD describes entities and relationships in a machine-readable form. Parsing JSON is separate from validating required search feature properties.
Match markup to visible content and validate it with a rich result testing tool. Eligibility does not guarantee display.
Targethttps://example.com/
Response HTML <head> / script[type=application/ld+json]
Use the example JSON in an application/ld+json script only when it matches the page. Fix existing JSON syntax first and validate any rich-result requirements separately.
0
{
"@context": "https://schema.org",
"@type": "WebPage",
"url": "https://example.com/",
"name": "Example Domain"
}There are no warning or unknown checks in this section.
No parseable JSON-LD was found.
Headings organize a page into a main topic and supporting sections. This tool checks for one H1 and shows the saved H2-H6 structure.
Use H1 for the main subject and H2/H3 for logical subsections, rather than selecting levels for visual size alone.
Targethttps://example.com/
Body h1 elements
If multiple H1s are shown, choose the main topic and use suitable subsection levels for the others. If absent, add the main heading near the start of content.
0
<h1>Main topic of this page</h1>
Alternative text conveys an image’s meaning. The count includes images with non-empty alt text.
Describe informative images in context. Empty alt="" can be appropriate for decorative images, so inspect their purpose before changing them.
The html lang attribute identifies the document’s primary language and helps assistive software select pronunciation.
Match lang to the main content and mark passages written in another language as appropriate.
The encoding declaration tells clients how to decode text. It must match the actual response bytes.
Keep the HTTP or HTML charset declaration consistent with the file encoding; use UTF-8 for UTF-8 content.
Tool reference range 15-70%; not an official ranking threshold.
This compares visible text length with HTML length. It cannot determine content quality or rankings on its own.
Do not add filler text to target a ratio. Check for useful HTML content and unnecessary markup.
There are no warning or unknown checks in this section.
Saved headings, up to 50 per level. Expand the H2-H6 lists when needed.
No H1 heading was found.
No headings at this level.
No headings at this level.
Up to 100 images are saved. Review an image’s purpose when its alt text is empty.
| URL | Image alt |
|---|
Word occurrence counts from extracted content, not search demand or keyword rankings.
Meta keywords · Not found
Meta keywords do not contribute to this tool’s score.
This counts links to the same site. Navigation and contextual links create routes to related information.
Link important pages with standard a href links and use text that describes the destination.
Targethttps://example.com/
nav / main
Add navigation or contextual links to real existing pages. Use a href rather than click-only elements.
0
<a href="[existing page path]">Describe the destination</a>
This heuristic detects query strings and underscores. Their presence does not make a URL invalid or unindexable.
Use understandable paths and manage redundant parameters. Review existing links and redirects before changing working URLs.
There are no warning or unknown checks in this section.
Up to 300 extracted links. Destination status codes and linked pages are not individually checked.
| URL | Link text | Attributes |
|---|
Viewport metadata enables device-width layouts. It is not a test of real mobile layout or touch targets.
Check width=device-width, then inspect overflow, zoom, forms and buttons on a small screen.
This detects a link declaration for a browser icon, rather than verifying its rendered appearance.
Check that the icon file loads and remains recognizable on light and dark browser surfaces.
This detects a touch icon declaration for saved home-screen shortcuts.
Review the icon’s dimensions, padding and background, then inspect it on an actual device.
Targethttps://example.com/
Response HTML <head>
Prepare a home-screen icon and declare its real path rather than adding a tag without a file.
<link rel="apple-touch-icon" href="/apple-touch-icon.png">
This detects WebP/AVIF from img src/srcset extensions and picture source types. Images whose format cannot be inferred from HTML, such as extensionless CDN URLs, may not be reflected in the count.
Compare quality and file size, and inspect the actual delivered format in browser developer tools.
This detects loading="lazy" on img elements. Pages with few images can pass the tool’s heuristic without it.
Consider lazy loading below-the-fold images while keeping prominent first-screen images promptly available.
There are no warning or unknown checks in this section.
The doctype declaration helps browsers render HTML in standards mode.
Place <!doctype html> at the start of the document and check for unintended output before it.
Tool heuristic: up to 4 external files
This counts external stylesheet declarations. Count alone does not measure transfer size, caching or render blocking.
Inspect duplicate or unused CSS and render blocking, then prioritize changes using actual performance measurements.
Tool heuristic: up to 6 external files
This counts script elements with src attributes. File count alone cannot measure execution cost or responsiveness.
Review duplicated scripts and expensive startup work; consider defer, async or delayed execution where appropriate.
This checks the HTML Content-Encoding header. Compression can reduce transfer size, with savings depending on the response.
Review text compression on the server or CDN, treating already compressed image formats separately.
Tool heuristic: at least 3 of 6 selected headers present
This detects selected security-related response headers. Their count does not establish policy quality or protection.
Review CSP, HSTS and other values for the application, then test for blocked resources or broken functionality.
Targethttps://example.com/
Web server / CDN response headers
These headers were absent. Configure response headers in the actual server/CDN settings: .htaccess or VirtualHost for Apache, or the Nginx server block. Validate the two example headers first; design CSP/HSTS for the real resources and HTTPS policy. The actual server configuration path is not visible to this tool.
strict-transport-security content-security-policy x-content-type-options x-frame-options referrer-policy permissions-policy
X-Content-Type-Options: nosniff Referrer-Policy: strict-origin-when-cross-origin
This checks whether the final analyzed page used HTTPS. It is not a security audit of the whole site.
Review certificate validity, mixed content and HTTPS on important linked pages and forms.
This checks whether a request starting over HTTP ends on HTTPS.
Configure consistent HTTP-to-HTTPS redirects and check for unnecessary chains or loops.
Targethttps://example.com/
HTTP host redirect configuration
Redirect the HTTP host to working HTTPS using 301/308 while preserving path and query.
http://example.com/
http://example.com/ → https://example.com/
These are HTML validation results from W3C Nu, not a ranking, accessibility or security certification.
Use message details and line numbers to investigate actual markup issues such as invalid nesting or missing attributes.
There are no warning or unknown checks in this section.
Up to 100 files per type are saved. File count alone does not establish a defect in any file.
| URL | HTML response location |
|---|---|
| https://example.com/s.js | 1 · /html/body/script |
No validation messages were reported.
This checks the robots.txt response. File presence does not verify all crawler permissions or actual indexing.
Review bot and path rules for your intended policy. Protect private information with authentication and access controls.
Targethttps://example.com/robots.txt
/robots.txt
Serve plain text at the domain root. Adapt this public-access example to your actual path and crawler policy.
User-agent: * Allow: / Sitemap: https://example.com/sitemap.xml
This detects a sitemap format at a declared or default URL. It does not crawl and validate every listed URL.
Include intended canonical URLs and meaningful update dates. Declare a custom sitemap location in robots.txt.
Targethttps://example.com/sitemap.xml
/sitemap.xml / robots.txt
Generate XML using real canonical URLs and declare the working location in robots.txt. Link an existing custom sitemap instead of duplicating it.
<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url><loc>https://example.com/</loc></url></urlset>
This checks for a text response at /llms.txt. Its presence does not guarantee use by an AI service or search visibility.
If you publish one, describe public resources accurately and keep its content and links current.
Targethttps://example.com/llms.txt
/llms.txt
If desired, publish UTF-8 text at the root and add real public documentation links. This is optional.
# Example Domain - [Home](https://example.com/)
This interprets root-path robots.txt rules for five bots. Training and search crawlers have different purposes; actual citations are not checked.
Decide access for each bot according to your policy rather than automatically allowing every crawler.
There are no warning or unknown checks in this section.
No robots.txt response was saved.
Run Google Lighthouse performance, accessibility, best practices and SEO checks. Device-specific results are cached for one day and are separate from the overall score above.
Locations refer to public HTML and resource URLs. Internal PHP or template file paths are not visible to external analysis.