eventsevllc.com

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

• Canonical URLmedium impactlow effort

  Canonical href is "/" (not an absolute URL)

  Crawlers resolve relative canonical URLs against whatever URL they happened to fetch, so a relative href can silently point your ranking signals at a parameterized or duplicate address. Replace it with the full absolute URL including scheme and host, e.g. <link rel="canonical" href="https://www.example.com/pricing/">. Generate it server-side from a configured base URL rather than from the incoming request's Host header, so staging domains and proxies can't leak into it.

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

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

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

• XML sitemap availablemedium impactlow effort

  sitemap.xml is valid but robots.txt does not reference it

  Your sitemap is valid, but robots.txt never mentions it, so crawlers you haven't manually notified may never find it — the robots.txt reference is the universal discovery mechanism. Add one line to robots.txt: "Sitemap: https://www.example.com/sitemap.xml", using the full absolute URL (a relative path is invalid here). The line can go anywhere in the file, and you can list several sitemaps. Also submit it in Google Search Console to get indexing-coverage reporting on top of discovery.

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