Skip to content
https://revenuebase.ai

SEO

· 14 checks — Canonical, meta, content depth, internal links, image SEO, and hreflang rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
0
REVIEW
0
PASS
13
INFO
1

Cross-tab audit — SEO, performance, crawlability, mobile, structured data

Checks
14
13 PASS
A+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://revenuebase.ai
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target returns 200
Canonical URL Configured
Page URL https://revenuebase.ai Canonical https://revenuebase.ai Match Self-referencing (correct) Target 200 ✓
A+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: RevenueBase | B2B Data Infrastructure to Grow Your Business
Info::
Title length (59 chars) is optimal
Info::
Meta description is 167 characters — truncated on mobile (~160 char limit)
Title

"RevenueBase | B2B Data Infrastructure to Grow Your Business"

59 characters Optimal ✓
Robots: Indexable (no restrictions)
A+
Title Style Depth
Title style is clean -- consistent separator, no stale year, no keyword stuffing
PASS
Title style is clean -- consistent separator, no stale year, no keyword stuffing
Info::
Title style is clean
A
Content Depth
2227 words, Difficult
PASS
2227 words, Difficult
Info::
Page has 2227 words — good depth for search engines
Info::
Text-to-HTML ratio is 3%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Difficult (grade 12)
2227 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 12

Text-to-HTML Ratio

3% text 97% HTML

14 KB / 536 KB

Very low ratio suggests heavy framework overhead or boilerplate.

Why this matters

Informational: ratio of visible text bytes to total HTML bytes. Very low ratios suggest excessive markup overhead.

A+
Image SEO
23 images, 23 descriptive filenames
PASS
23 images, 23 descriptive filenames
Info::
All images have descriptive filenames
23 descriptive
0 hash-based
0 generic
23 total
All images have descriptive filenames and proper SEO attributes.

See Accessibility tab for detailed alt text quality analysis.

A+
Hreflang URL Quality
No hreflang tags on the page
PASS
No hreflang tags on the page
Info::
No hreflang tags on the page
A+
Hreflang Completeness
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
PASS
No hreflang tags on this page -- check is N/A (single-language site or unannotated)
Info::
No hreflang tags found -- completeness check is N/A
A+
Sitemap Freshness
Sitemap updated within 90 days (80/80 URLs have lastmod)
PASS
Sitemap updated within 90 days (80/80 URLs have lastmod)
Info::
Sitemap actively maintained — newest lastmod: 24 days ago
Got: 2026-09-09T02:04:38Z
A+
Sitemap × Robots Consistency
No sitemap-vs-robots conflicts detected
PASS
No sitemap-vs-robots conflicts detected
Info::
Sitemap URLs are not blocked by robots.txt
A+
Sitemap Hygiene
Sitemap structure / size look healthy (80 URLs, 13 KB)
PASS
Sitemap structure / size look healthy (80 URLs, 13 KB)
Info::
Sitemap structure / size look healthy (80 URLs)
A
Markup Quality
2 markup-quality issue(s) detected
PASS
2 markup-quality issue(s) detected
Info::
`<meta charset>` declared at byte 8387 -- past the 1024-byte spec window
The HTML5 spec requires the encoding declaration to appear in the first 1024 bytes. Browsers that started parsing in a default encoding and discover the real charset later DISCARD parsing state and re-parse from the top -- a measurable hit to First Contentful Paint. Move the `<meta charset>` tag to be the first child of `<head>`.
Info::
1 redundant ARIA role attribute(s) on native semantic element(s)
The W3C "ARIA in HTML" spec calls this its first rule: don't use ARIA when a native HTML element already conveys the semantics. `<button role="button">`, `<a href role="link">`, `<nav role="navigation">`, `<main role="main">` -- the role attribute either does nothing or shadows the native semantic, occasionally breaking assistive-tech behaviors. Remove the redundant role.
A+
Schema Markup Audit
2 schema types detected
PASS

Rich result eligibility

Organization Eligible

Organization knowledge panel

FAQPage Eligible

FAQ rich results

Detected schema types

Organization json-ld → Organization knowledge panel
2/2 required · 1/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Add a logo URL (square, ≥112px) Strongly recommended — appears in the knowledge panel header
  • sameAs — Add sameAs URLs for social profiles Connects the entity across the web
  • contactPoint — Add ContactPoint with telephone and contactType Enables direct contact from the knowledge panel
  • description — Used as the panel summary
Google's spec for this type
FAQPage json-ld → FAQ rich results
1/1 required
Required fields (Google)
  • mainEntity — Required — without this the FAQ schema is invalid
Google's spec for this type

Adding these recommended fields improves chances of getting Organization knowledge panel in search results.

Why this matters

Schema entity has required fields but could add recommended ones for richer SERP layouts (star ratings, prices, etc.).

Source: Google Search Central

Hreflang
0 hreflang tags
INFO
0 hreflang tags

No hreflang tags detected.

Hreflang tags are only needed for multilingual or multi-regional sites.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback