SEO report

SEO report for moz.com

https://moz.com/ · checked Sun, 01 Nov 2026 14:05 GMT

✓ 32 Passed! 8 Warnings✗ 7 FailedAI readiness 94%

Fix these first

  1. Render-blocking resourceshigh

    1 blocking script(s) and 5 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

    See the details

  2. H1 headingcritical

    “Show up in search. Show up in AI. Own the results.”

    Fix: Use one H1 that states the page topic with its main keyword.

    See the details

  3. Heading structuremedium

    57 headings for 1974 words – a lot for the amount of text.

    Fix: Use H2s for main sections and H3s inside them, without skipping levels.

    See the details

  4. Imagesmedium

    49 image(s).

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

    See the details

  5. Form labelsmedium

    2 of 2 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

    See the details

  6. Tap-to-contactmedium

    No tel: or mailto: links.

    Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

    See the details

  7. Meta descriptionhigh

    187 characters, ~1169px of ~990px.

    Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

    See the details

  8. Broken links (sample)high

    Checked 12 internal link(s).

    Fix: Fix or remove links that return errors, and update links that redirect.

    See the details

Check the whole website

This report covers one page. The full-site audit crawls up to 250 pages to find broken links, duplicate titles, orphan pages and more.

Run a full-site audit

Monitor this site weekly

We'll re-check it every week and track the score, with a history graph and a list of anything that breaks.

Compare with competitors

See how this page scores against up to two competitors, side by side, and where they beat you.

Compare sites

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to moz.com…

Indexing & crawling 100%

Can search engines reach, read and index this page?

  • ✓

    Status codecritical

    The page returned HTTP 200.

  • ✓

    Indexablecritical

    No noindex instruction – the page can appear in search.

  • ✓

    robots.txthigh

    robots.txt found.

    Googlebot is allowed to crawl this page.

  • ✓

    XML sitemaphigh

    Sitemap index found at https://moz.com/sitemaps-1-sitemap.xml listing 55 sitemaps.

    Declared in robots.txt.

    Most recent lastmod: 2026-10-30T13:38:33-07:00.

  • ✓

    Canonical URLhigh

    Canonical: https://moz.com/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✓

    www / non-wwwmedium

    www.moz.com redirects to moz.com.

Search snippet & sharing 79%

How the page looks in Google results and when shared.

  • ✓

    Title tagcritical

    “Moz - SEO Software for Smarter Marketing”

    About 381px of Google's ~580px desktop width.

  • !

    Meta descriptionhigh

    187 characters, ~1169px of ~990px.

    Long – Google will probably truncate it.

    Google sometimes rewrites descriptions to match the search; a good one is still used most often.

    Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  • ✓

    Open Graph & social cardsmedium

    Open Graph title and image set.

    Twitter/X card: summary_large_image.

  • ✗

    Faviconlow

    No favicon linked.

    Fix: Add a square favicon at least 48×48px.

  • ✓

    Languagelow

    lang="en-US"

Content quality 70%

Is there enough clear, useful text that matches what the page targets?

  • ✓

    Word countmedium

    1,974 words of main content (inside <main>).

    Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

  • ✓

    Readabilitymedium

    Flesch reading ease 53 (fairly easy), about 13 words per sentence.

  • ✓

    Topic focushigh

    3 of 4 title keywords appear in the main content (missing: smarter).

  • !

    H1 headingcritical

    “Show up in search. Show up in AI. Own the results.”

    The H1 shares no keywords with the title.

    Fix: Use one H1 that states the page topic with its main keyword.

  • ✗

    Heading structuremedium

    57 headings for 1974 words – a lot for the amount of text.

    6 skipped level(s), e.g. H2 → H4.

    Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  • ✓

    Text-to-code ratiolow

    10% of the HTML is visible text.

AI search readiness 94%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

  • ✓

    AI crawler accesshigh

    Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

  • ✓

    Snippet controlshigh

    No snippet restrictions – search and AI answers can quote this page.

  • ✗

    llms.txtlow

    No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.

    Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.

  • ✓

    Question-led contentmedium

    5 heading(s) phrased as questions, e.g. “Why marketers trust Moz Data & tools”.

  • ✓

    Entity clarityhigh

    Identified as: Organization.

    5 official profile link(s) (sameAs).

  • ✓

    Freshness signalsmedium

    The page shows when it was published or last updated.

  • ✓

    Trust pages (E-E-A-T)medium

    Links found to all three: about, contact and privacy.

Structured data 100%

Machine-readable facts for rich results and AI.

  • ✓

    JSON-LD present & validhigh

    1 JSON-LD block(s): WebPage, ImageObject, Organization, PostalAddress, BreadcrumbList, ListItem.

    All blocks parse correctly.

  • ✓

    Required propertiesmedium

    Key types include Google's required properties.

  • i

    Breadcrumbslow

    Home page – breadcrumbs not needed.

Performance 50%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

  • ✓

    Server response (TTFB)high

    34 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  • !

    HTML sizemedium

    161 kB of HTML.

    Fix: Remove inline bloat, base64 images and unused markup.

  • i

    Compressionmedium

    Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

  • ✗

    Render-blocking resourceshigh

    1 blocking script(s) and 5 stylesheet(s) in <head>.

    Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  • !

    Scripts & third partiesmedium

    17 script tag(s); files loaded from 3 other domain(s): cdn.ziffstatic.com, cloud.wordlift.io, static.cloudflareinsights.com.

    Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  • ✗

    Imagesmedium

    49 image(s).

    13 without width/height – can cause layout shift (CLS).

    10 image(s) after the first three aren't lazy-loaded.

    7 use WebP/AVIF or responsive srcset.

    Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  • ✓

    Cachinglow

    Cache-Control: public, max-age=3600

  • ✓

    HTTP/3low

    Server advertises HTTP/3 (faster on mobile networks).

Security 88%

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • !

    HSTSmedium

    HSTS: max-age=2592000

    max-age is under 6 months – browsers will forget it quickly.

    Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  • !

    Security headerslow

    Present: nosniff, Referrer-Policy, clickjacking protection.

    Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  • ✓

    Server fingerprintlow

    No X-Powered-By header (server: cloudflare).

Mobile & accessibility 67%

Usable on phones and by everyone – Google indexes the mobile version.

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1

  • ✓

    Image alt textmedium

    All 49 images have alt text.

  • ✗

    Form labelsmedium

    2 of 2 form field(s) have no label.

    Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

  • ✗

    Tap-to-contactmedium

    No tel: or mailto: links.

    Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

Local SEO not scored

This site doesn't look like a local business, so these checks are shown for information and not scored.

  • i

    LocalBusiness markuphigh

    No LocalBusiness structured data.

  • i

    Contact details on pagemedium

    No phone number found.

    No postcode found (fine for service-area businesses).

  • i

    Map & directionslow

    No map or directions link.

This report checks one page. Scores are a guide, not a guarantee of rankings. Check another page · Print or save as PDF

Want these fixed for you? XKey is made by IceWork, a Blackpool web studio. IceWork builds fast websites that pass every check here – a 3-page site with domain and a year's hosting is £350 all in.