This report covers an on-page SEO audit of go.drveri.com, checked on August 28, 2026. Across 29 individual checks spanning indexing and meta tags, content structure, social and structured data, security, and technical fundamentals, the page scored 91/100 — overall, its on-page SEO health is strong.
Nothing failed outright, but there are 5 warnings worth a look, including Readability, X-Content-Type-Options, and Clickjacking protection. None of these are critical alone, but resolving them would round out the page's SEO fundamentals. Indexing & meta, Social & structured data, and Technical were entirely clean, with no issues in that area at all.
requested: https://go.drveri.com
HTTP 200 · checked Aug 28, 2026 at 16:50 UTC · this report is permanent — re-checking creates (or reuses) a fresh one
91
24 passed ·
5 warnings ·
0 failed
Page Information
Title
Best Websites Directory — Hand-Picked Sites by Category
Meta description
Explore hand-picked websites across dozens of categories — technology, business, entertainment, travel, and more — each with an in-depth, independent write-up.
Valid JSON-LD structured data enables rich results (star ratings, FAQs, breadcrumbs) in search listings.
✓
Favicon
Icon link present
A missing favicon makes a site look unfinished in browser tabs, bookmarks, and some search results.
Security
✓
Strict-Transport-Security
max-age=31536000; includeSubDomains
HSTS forces browsers to always use HTTPS for this site, closing a downgrade-attack window.
!
X-Content-Type-Options
Missing — add "nosniff" to stop MIME-sniffing
Stops browsers from "MIME sniffing" a response into an unintended, potentially unsafe content type.
Suggestion: Add the header "X-Content-Type-Options: nosniff".
!
Clickjacking protection
No X-Frame-Options or CSP frame-ancestors directive
Without this, the page can potentially be embedded in a malicious iframe to trick users into clicking things.
Suggestion: Add "X-Frame-Options: SAMEORIGIN" or a CSP frame-ancestors directive.
!
Content-Security-Policy
Not set
A CSP restricts what scripts/resources a page can load, reducing the damage a XSS bug could do.
Suggestion: Define a Content-Security-Policy header appropriate to the site's actual resources.
!
Referrer-Policy
Not set — defaults vary by browser
Controls how much URL information leaks to other sites when a user clicks an outbound link.
Suggestion: Add a Referrer-Policy header, e.g. "strict-origin-when-cross-origin".
✓
Mixed content
No insecure subresources found
Browsers block or warn on insecure resources loaded by an HTTPS page, which can silently break functionality.
Technical
✓
HTTP status
200 OK (25 ms)
Search engines need a clean 200 response to crawl and index a page at all.
✓
Redirect chain
No redirects — direct 200
Every redirect hop adds latency and dilutes link equity slightly; long chains can also confuse crawlers.
✓
HTTPS
Served over HTTPS
Google uses HTTPS as a ranking signal, and browsers flag plain HTTP pages as "Not secure".
✓
Charset declared
utf-8
Without a declared charset, browsers may guess wrong and render text incorrectly.
✓
Mobile viewport
Viewport meta tag present
Google indexes the mobile version of pages first — without a viewport tag, mobile rendering breaks.
✓
HTML language
lang="en"
The lang attribute tells search engines and screen readers what language the content is in.
✓
robots.txt
Present and reachable · declares 2 sitemap(s)
robots.txt controls which parts of a site crawlers are allowed to access at all.
✓
sitemap.xml
Present at /sitemap.xml — 280 URLs listed
A sitemap helps search engines discover every page, especially ones with few internal links pointing to them.
Suggestions to Improve SEO
1ReadabilityMedium priority
Shorten sentences, swap jargon-heavy words for plainer ones, and break long paragraphs into shorter ones with more whitespace between them. A good gut check: read it aloud — if you run out of breath mid-sentence, it's probably too long.
2X-Content-Type-OptionsMedium priority
Add the response header "X-Content-Type-Options: nosniff" at the web server or application level. This is typically a one-line config change (an nginx add_header directive or equivalent) with no visible impact on the site.
3Clickjacking protectionMedium priority
Add "X-Frame-Options: SAMEORIGIN", or a Content-Security-Policy with frame-ancestors 'self', as a response header. Like the header above, this is a low-effort server config change that closes off a real attack vector without affecting how the page looks or works.
4Content-Security-PolicyMedium priority
Define a Content-Security-Policy header that allows only the script, style, and resource origins your site actually uses. Start permissive and tighten it once you've confirmed nothing breaks, rather than trying to write a perfect policy up front — your browser's console will show exactly what a strict policy blocks.
5Referrer-PolicyMedium priority
Add a Referrer-Policy header such as "strict-origin-when-cross-origin", a sensible default that still lets analytics see referring domains without leaking full URLs — including any sensitive path or query data — to third-party sites you link to.
Overall, go.drveri.com is in reasonably good shape — nothing is broken, but resolving the 5 warnings above would move this from a solid foundation to a well-optimized page. Re-run this check after making changes to track progress.
Own this site, or want the latest numbers? Run a fresh check — a repeat check within 10 minutes reuses this same report.