SEOWebsiteTool
67Grade C

filtrae.shop

Parked Domain name on Hostinger DNS system

6 failed · 6 warnings · 17 passed

Audited Sun, 12 Jul 2026 10:01:00 GMT · https://filtrae.shop/

Meta & Head

11.8/25

Title, description, canonical, social tags — what search engines read first.

  • Meta descriptionhigh impactlow effort

    No meta description found

    The meta description is your ad copy in search results; without one, engines pull an arbitrary snippet from the page, which usually reads poorly and costs you clicks. Add <meta name="description" content="..."> with 70–160 characters that summarize the page and give a concrete reason to click — what the visitor gets plus a differentiator (free, instant, no signup). Write a unique description per page: one duplicated across the site is treated much like a missing one.

  • Page allows indexinghigh impactlow effort

    <meta name="robots" content="noindex, nofollow, noarchive, nosnippet">

    This page tells search engines not to index it, so it can never rank — every other optimization is wasted while this tag is present. If that's unintentional, remove the noindex directive (or the whole robots meta tag) and request re-indexing in Google Search Console. A common pitfall: staging noindex tags shipped to production during a launch.

  • Open Graph tagsmedium impactlow effort

    No Open Graph tags found

    Open Graph tags control how your page looks when shared on Facebook, LinkedIn, Slack, WhatsApp, and most chat apps; without them, links render as a bare URL or with guessed text, and far fewer people click through. Add four meta tags to <head>: og:title, og:description, og:url, and og:image — an image around 1200x630 pixels works well across platforms. Use absolute https:// URLs for og:image and og:url; relative paths are the most common reason preview images silently fail to appear.

  • Canonical URLmedium impactlow effort

    No <link rel="canonical"> found

    When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.

  • Twitter card taglow impactlow effort

    No twitter:card meta tag found

    X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.

4 passing checks
  • Title tag<title> is "Parked Domain name on Hostinger DNS system" (42 characters)
  • Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
  • Character encoding declaredCharacter encoding is declared
  • FaviconNo <link rel="icon">, but /favicon.ico responds with 200

Content & Structure

20.3/25

Headings, copy depth, images, structured data, internal linking.

  • Internal linkingmedium impactmedium effort

    0 internal, 5 external links

    Search engines discover and rank your pages by following internal links; a page with none is a dead end for crawlers and visitors alike. Add contextual links to related pages on your own site — navigation, related-content sections, and in-body links all count. Aim for at least a handful of relevant internal links per page.

  • Structured data (JSON-LD)medium impactmedium effort

    No JSON-LD structured data blocks found

    Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.

6 passing checks
  • Single H1 heading1 h1 found: ""
  • Heading hierarchy7 headings in order without skipped levels
  • Word count1558 words of visible text
  • Image alt text1 of 1 images have alt text
  • HTML lang attribute<html lang="en">
  • JavaScript-dependent contentvisible text ~912 chars in the initial HTML

Technical

18.2/25

HTTPS, redirects, robots, sitemap, speed, crawlability.

  • robots.txt present and permissivemedium impactlow effort

    robots.txt disallows all crawling

    Your robots.txt contains a blanket "Disallow: /", which tells every search engine to stay out — your pages cannot be crawled and will not rank while this rule is in place. This is usually a staging-environment setting that shipped to production by accident. Replace the blanket rule with targeted ones, e.g. "Disallow: /admin/" for areas you genuinely want excluded, or remove it entirely if everything should be crawlable. Note that Disallow only blocks crawling, not indexing — use a noindex meta tag for pages you want out of results.

  • XML sitemap availablemedium impactlow effort

    sitemap.xml exists but is not valid XML

    Your sitemap exists but isn't valid XML, so search engines reject the whole file and you get none of its discovery benefit — worse than having no sitemap, because you probably believe it's working. Regenerate it with your framework's built-in generator or a sitemap library rather than hand-editing; unescaped ampersands in URLs (& instead of &amp;) are the most common breakage. Validate before deploying, and check the Sitemaps report in Google Search Console afterwards — it surfaces parse errors explicitly.

  • HTTP redirects to HTTPSmedium impactlow effort

    http:// version serves content without redirecting

    Your http:// URLs serve content instead of redirecting, so search engines can crawl and index two parallel copies of every page and split ranking signals between them. Add a permanent 301 redirect from http to https at the server or CDN level — in nginx, "return 301 https://$host$request_uri;" in the port-80 server block; in Apache, a RewriteRule in .htaccess; on Cloudflare, enable "Always Use HTTPS". Use a 301, not a 302 — temporary redirects don't consolidate ranking signals — and preserve the full path in the redirect target.

  • Response compression enabledlow impactlow effort

    no content-encoding header

    This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.

  • Missing pages return 404low impactlow effort

    missing paths return a non-404 status (soft 404)

    URLs that don't exist on your site return a success status instead of 404 — search engines call these soft 404s, keep recrawling them, and may index the useless placeholder pages, wasting crawl budget that should go to real content. Configure your server or framework to return an actual 404 status (or 410 for permanently removed content) along with your error page. The classic mistake is serving a friendly "page not found" template with a 200 status — crawlers ignore the visible message; only the status code counts.

7 passing checks
  • Served over HTTPSfinal URL uses https://
  • No mixed content0 http:// subresource references
  • Short redirect chainno redirects; URL resolves directly
  • Fast time to first byte75 ms
  • Reasonable HTML size31.3 KB
  • www and non-www resolve consistentlywww and non-www converge on the same host
  • HTML5 doctype<!DOCTYPE html> present

Performance

Core Web Vitals scoring via Google PageSpeed is coming soon.

Share your score

Embed this live badge on your site — it updates whenever the audit is re-run.

SEO score badge for filtrae.shop

More “f” sitesRecent audits

filtrae.shop — SEO Score 67/100 (Grade C) | SEO Website Tool