SEO report for algorithmwatch.org

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 algorithmwatch.org…

Indexing & crawling 73%

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

  No XML sitemap found at /sitemap.xml or in robots.txt.

  Fix: Create an XML sitemap listing every page and submit it in Google Search Console.

  On WordPress: WordPress makes one at /wp-sitemap.xml, and Yoast or Rank Math make /sitemap_index.xml. Submit it in Google Search Console.

  Make one with the free XML sitemap generator

  Read the guide: XML sitemaps

• !

  Canonical URLhigh

  Canonical: https://algorithmwatch.org/en/

  Points to a DIFFERENT address – Google will probably index that one instead of this page.

  Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  Read the guide: duplicate content

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✗

  www / non-wwwmedium

  Both www.algorithmwatch.org and algorithmwatch.org load without redirecting – Google may see duplicate sites.

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

Search snippet & sharing 54%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “AlgorithmWatch”

  About 141px of Google's ~580px desktop width – short; use the space.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✗

  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.

  On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the meta description.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary_large_image.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="en"

Content quality 50%

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

• ✓

  Word countmedium

  1,150 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 34 (fairly difficult), about 19 words per sentence.

  Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  Read the guide: how to write SEO content

• i

  Topic focushigh

  No title keywords to compare.

• !

  H1 headingcritical

  13 H1 headings – one clear H1 is best practice.

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

  On WordPress: Most themes show the page title as the H1. In the editor, make sure no other block uses Heading 1 – use Heading 2 for sections.

• ✗

  Heading structuremedium

  92 headings for 1150 words – a lot for the amount of text.

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

  10 empty heading(s).

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

  Read the guide: the on-page SEO checklist

• !

  Text-to-code ratiolow

  5% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 63%

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.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• ✓

  Question-led contentmedium

  7 heading(s) phrased as questions, e.g. “What is algorithmic discrimination?”.

• ✗

  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.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✗

  Freshness signalsmedium

  No published/updated date found.

  Fix: Show a 'last updated' date and add dateModified to your structured data.

• ✓

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

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

Structured data 0%

Machine-readable facts for rich results and AI.

• ✗

  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).

  Make valid code with the free schema generator

  Read the guide: schema markup

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  95 internal and 23 external links.

• ✗

  Anchor text qualitymedium

  Same text used for different pages: “read more”, “auf deutsch lesen”.

  8 vague link(s) like “click here” or “read more”.

  2 link(s) with no text at all.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

  1 link(s) point to a redirect – link to the final address instead.

Performance 40%

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

• !

  Server response (TTFB)high

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

  Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

• !

  HTML sizemedium

  178 kB of HTML.

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

• ✓

  Compressionmedium

  Compressed with gzip.

• ✗

  Render-blocking resourceshigh

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

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

  Read the guide: Core Web Vitals

• !

  Scripts & third partiesmedium

  13 script tag(s); files loaded from 0 other domain(s).

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

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  40 image(s).

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

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

  28 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.

  On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.

  Read the guide: image SEO

• !

  Cachinglow

  Cache-Control: max-age=3, must-revalidate

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• 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 92%

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=31536000; includeSubDomains

• ✗

  Security headerslow

  Present: none.

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

  Read the guide: the technical SEO checklist

• ✓

  Server fingerprintlow

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

Mobile & accessibility 58%

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

• ✓

  Mobile viewportcritical

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

• ✓

  Image alt textmedium

  All 40 images have alt text.

• ✗

  Form labelsmedium

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

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

• ✗

  Link nameslow

  2 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✗

  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.

  Read the guide: mobile-friendly websites

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.