SEO report

SEO report for hayward-ca.gov

https://hayward-ca.gov/ · checked Sun, 01 Nov 2026 19:40 GMT

✓ 28 Passed! 4 Warnings✗ 14 FailedAI readiness 50%Built with Drupal

Fix these first

  1. Meta descriptionhigh

    No meta description – Google will pick text from the page.

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

    See the details

  2. Entity clarityhigh

    No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

    See the details

  3. JSON-LD present & validhigh

    No JSON-LD structured data.

    Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

    See the details

  4. Render-blocking resourceshigh

    0 blocking script(s) and 25 stylesheet(s) in <head>.

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

    See the details

  5. H1 headingcritical

    4 H1 headings – one clear H1 is best practice.

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

    See the details

  6. www / non-wwwmedium

    Both www.hayward-ca.gov and hayward-ca.gov load without redirecting – Google may see duplicate sites.

    Fix: Pick one version (with or without www) and 301-redirect the other to it.

    See the details

  7. Open Graph & social cardsmedium

    Open Graph title or image missing.

    Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

    See the details

  8. Heading structuremedium

    40 headings for 584 words – a lot for the amount of text.

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

    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 hayward-ca.gov…

Indexing & crawling 87%

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 found at https://hayward-ca.gov/sitemap.xml with 1 URL.

    Not declared in robots.txt.

    This page is NOT listed in it.

    No lastmod dates – add accurate ones so search engines know what changed.

    Fix: Add a 'Sitemap:' line to robots.txt, list every indexable page and include accurate lastmod dates.

  • ✓

    Canonical URLhigh

    Canonical: https://hayward-ca.gov/

    Points to this page (self-referencing).

  • ✓

    Redirectshigh

    Loads directly with no redirects.

  • ✗

    www / non-wwwmedium

    Both www.hayward-ca.gov and hayward-ca.gov load without redirecting – Google may see duplicate sites.

    Fix: Pick one version (with or without www) and 301-redirect the other to it.

  • ✓

    hreflangmedium

    1 hreflang link(s).

    All language codes are valid.

    No x-default (recommended for a language picker or fallback page).

Search snippet & sharing 58%

How the page looks in Google results and when shared.

Content quality 70%

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

  • ✓

    Word countmedium

    584 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 72 (plain English), about 13 words per sentence.

  • ✓

    Topic focushigh

    4 of 5 title keywords appear in the main content (missing: official).

  • !

    H1 headingcritical

    4 H1 headings – one clear H1 is best practice.

    The H1 shares no keywords with the title.

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

  • ✗

    Heading structuremedium

    40 headings for 584 words – a lot for the amount of text.

    3 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 50%

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.

    Training-only crawlers blocked: GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot, meta-externalagent. That's a licensing choice – these companies document them as separate from their search crawlers.

  • ✓

    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

    No headings phrased as questions.

    Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  • ✗

    Entity clarityhigh

    No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

    Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  • ✓

    Freshness signalsmedium

    The page shows when it was published or last updated.

  • ✗

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

    Links found to privacy; missing about and contact.

    Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 0%

Machine-readable facts for rich results and AI.

Performance 54%

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

  • ✓

    Server response (TTFB)high

    57 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

    77 kB of HTML.

  • 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

    0 blocking script(s) and 25 stylesheet(s) in <head>.

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

  • !

    Scripts & third partiesmedium

    22 script tag(s); files loaded from 4 other domain(s): googletagmanager.com, cdnjs.cloudflare.com, use.fontawesome.com, youtube.com.

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

  • ✗

    Imagesmedium

    11 image(s).

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

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

    0 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: max-age=300, public

  • i

    HTTP/3low

    Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 75%

Visitor safety signals that browsers and Google check.

  • ✓

    HTTPScritical

    Secure HTTPS with no mixed content.

  • ✓

    HTTP → HTTPS redirecthigh

    http:// redirects to https://.

  • ✗

    HSTSmedium

    No Strict-Transport-Security header.

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

  • ✗

    Security headerslow

    Present: nosniff, 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 83%

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

  • ✓

    Mobile viewportcritical

    viewport: width=device-width, initial-scale=1, shrink-to-fit=no

  • ✓

    Image alt textmedium

    All 11 images have alt text.

  • ✓

    Form labelsmedium

    All 2 form fields are labelled.

  • ✗

    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.