SEO report for www.saynoto0870.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 saynoto0870.com…

Indexing & crawling 75%

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.

  Make one with the free XML sitemap generator

  Read the guide: XML sitemaps

• ✗

  Canonical URLhigh

  No canonical tag.

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

  Read the guide: duplicate content

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://saynoto0870.com/ → https://www.saynoto0870.com/

  A single redirect to your preferred address is normal; just make sure your own links use the final address.

• ✓

  www / non-wwwmedium

  saynoto0870.com redirects to www.saynoto0870.com.

Search snippet & sharing 17%

How the page looks in Google results and when shared.

• ✗

  Title tagcritical

  “SAYNOTO0870.COM - Non-Geographical Alternative Telephone Numbers”

  About 661px of Google's ~580px desktop width – it will probably be cut off.

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

  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.

  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.

• ✗

  Faviconlow

  No favicon linked.

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

• ✗

  Languagelow

  No lang attribute on <html>.

  Fix: Add lang="en-GB" (or your language) to the <html> tag.

Content quality 60%

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

• ✓

  Word countmedium

  854 words of main content (menus and footer excluded).

  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 19 words per sentence.

• ✓

  Topic focushigh

  6 of 6 title keywords appear in the main content.

• ✗

  H1 headingcritical

  No H1 heading.

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

• !

  Heading structuremedium

  0 headings for 854 words.

  Levels are in order.

  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

  23% of the HTML is visible text.

AI search readiness 44%

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

  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.

  Read the guide: how to write SEO content

• ✗

  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 contact and privacy; missing about.

  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.

• ✗

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

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  17 internal and 23 external links.

• !

  Anchor text qualitymedium

  Same text used for different pages: “here”.

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

  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.

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

• !

  Internal links to http://medium

  4 internal link(s) use http:// – each one goes through a redirect.

  Fix: Update internal links to use https:// (or relative links).

Performance 69%

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

• ✓

  Server response (TTFB)high

  796 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

  22 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 0 stylesheet(s) in <head>.

• !

  Scripts & third partiesmedium

  16 script tag(s); files loaded from 2 other domain(s): fundingchoicesmessages.google.com, pagead2.googlesyndication.com.

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

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  15 image(s).

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

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

  Read the guide: image SEO

• ✗

  Cachinglow

  No Cache-Control header.

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

  Read the guide: the technical SEO checklist

• ✗

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

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

• ✗

  Mobile viewportcritical

  No viewport meta tag – the page won't fit phones.

  Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

  Read the guide: mobile-friendly websites

• ✓

  Image alt textmedium

  All 15 images have alt text.

• ✓

  Link nameslow

  Every link has a readable name.

• ✗

  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.