cleobetra-vip-au.com

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

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

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

• Structured data (JSON-LD)medium impactmedium effort

  7 JSON-LD block(s) present but none usable — block 1: Expected double-quoted property name in JSON at position 692 (line 16 column 7); block 2: Expected double-quoted property name in JSON at position 692 (line 16 column 7); block 3: Expected double-quoted property name in JSON at position 692 (line 16 column 7); block 4: Expected double-quoted property name in JSON at position 692 (line 16 column 7); block 5: Expected double-quoted property name in JSON at position 692 (line 16 column 7); block 6: Expected double-quoted property name in JSON at position 692 (line 16 column 7); block 7: Expected double-quoted property name in JSON at position 692 (line 16 column 7)

  This page ships JSON-LD blocks, but they're malformed or missing an @type, so search engines discard them entirely — you get zero rich-result benefit from work that's already been done. Fix the JSON syntax (trailing commas and unescaped quotes are the usual culprits) and give every block a valid schema.org @type, e.g. {"@context": "https://schema.org", "@type": "Article", ...}. Validate with Google's Rich Results Test before deploying — a block that parses locally can still fail Google's stricter requirements for required properties.

• Image alt textmedium impactlow effort

  37 of 48 images have alt text

  Alt text is how search engines understand what an image shows — it feeds image-search rankings and is what screen readers announce to blind visitors. Add a short, specific alt attribute to every meaningful image, describing the content rather than listing keywords: alt="Golden retriever puppy playing in snow" beats alt="dog puppy pet animal". Give purely decorative images an empty alt="" instead of omitting the attribute, so assistive technology knows to skip them rather than reading out the filename.

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

• Fast time to first bytehigh impactmedium effort

  1523 ms

  Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.

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