SEO report for parseur.com

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 parseur.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://parseur.com/sitemap.xml listing 9 sitemaps.

  Declared in robots.txt.

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

• ✓

  Canonical URLhigh

  Canonical: https://parseur.com/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.parseur.com redirects to parseur.com.

• ✓

  hreflangmedium

  13 hreflang link(s).

  All language codes are valid.

Search snippet & sharing 88%

How the page looks in Google results and when shared.

• ✓

  Title tagcritical

  “AI data extraction software | Parseur®”

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

• !

  Meta descriptionhigh

  177 characters, ~1088px 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.

  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-US"

Content quality 80%

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

• ✓

  Word countmedium

  1,727 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 56 (fairly easy), about 12 words per sentence.

• ✓

  Topic focushigh

  3 of 3 title keywords appear in the main content.

• !

  H1 headingcritical

  “Intelligent document processing you can trust”

  The H1 shares no keywords with the title.

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

• ✓

  Heading structuremedium

  25 headings for 1727 words.

  Levels are in order.

• !

  Text-to-code ratiolow

  8% of the HTML is visible text.

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

AI search readiness 81%

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

  /llms.txt found.

• !

  Question-led contentmedium

  2 heading(s) phrased as questions, e.g. “Why use Parseur instead of building it yourself”.

  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.

  Read the guide: how to write SEO content

• ✓

  Entity clarityhigh

  Identified as: Organization, Person.

  4 official profile link(s) (sameAs).

• ✗

  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 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  3 JSON-LD block(s): Organization, Person, PostalAddress, ContactPoint, Certification, SoftwareApplication, AggregateRating, Offer, PropertyValue, FAQPage, Question, Answer.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

  Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 100%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  147 internal and 36 external links.

• ✓

  Anchor text qualitymedium

  No link text points to two different pages.

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

Performance 65%

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

• ✓

  Server response (TTFB)high

  194 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

  229 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

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

• !

  Scripts & third partiesmedium

  23 script tag(s); files loaded from 4 other domain(s): googletagmanager.com, kit.fontawesome.com, static.senja.io, static.cloudflareinsights.com.

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

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  70 image(s).

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

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

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

  Read the guide: image SEO

• !

  Cachinglow

  Cache-Control: public, max-age=0, 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 96%

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; preload

• !

  Security headerslow

  Present: nosniff, Referrer-Policy.

  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 100%

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 70 images have alt text.

• ✓

  Form labelsmedium

  All 8 form fields are labelled.

• ✓

  Link nameslow

  Every link has a readable name.

• ✓

  Tap-to-contactmedium

  One-tap contact: phone.

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

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

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist