Skip to content
https://www.render.com

SEO

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

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

Checks
7
5 PASS 1 REVIEW
C
Content Depth
Action
737 words, Very Difficult
REVIEW
737 words, Very Difficult
Info::
Page has 737 words of content
Info::
Text-to-HTML ratio is 1%
Very low ratio suggests heavy framework overhead or boilerplate.
Info::
Reading level: Very Difficult (grade 15)
737 words

Good depth

Reading level

Very Easy
Easy
Fairly Easy
Standard
Fairly Difficult
Difficult
Very Difficult

Grade 15

Text-to-HTML Ratio

1% text 99% HTML

5 KB / 667 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+
Canonical URL
Properly configured
PASS
Properly configured
Info::
Canonical tag present
Got: https://render.com
Info::
Canonical is self-referencing
Info::
Canonical matches final URL after redirects
Info::
Canonical target reachable (self-referencing)
Info::
Canonical points to a different domain
Canonical URL Problem
Page URL https://www.render.com Canonical https://render.com Match Self-referencing (correct)
A+
Meta Tags
Title optimized
PASS
Title optimized
Info::
Page title is set
Got: <!---->Close Cookie Preferences<!---->
Info::
Title length (38 chars) is optimal
Info::
Title and H1 have very different wording
Alignment helps users confirm they've reached the right page.
Title

"<!---->Close Cookie Preferences<!---->"

38 characters Optimal ✓
Title: <!---->Close Cookie Preferences<!---->
H1: Your fastest path to production forany workload
Match: Very different
Robots: Indexable (no restrictions)

Alignment helps users confirm they've reached the right page.

Why this matters

Title and H1 disagree significantly — Google may treat one as the canonical topic and the other as off-topic, weakening ranking.

Learn more

Title is the SERP headline; H1 is the on-page headline. They should describe the same page. Large divergence (different topics, different keywords) signals confusion and Google may rewrite the title in SERP. Align both to the same primary topic.

Source: Google Search Central / on-page SEO

A+
Image SEO
54 images, 53 descriptive filenames
PASS
54 images, 53 descriptive filenames
Info::
1 image(s) have hash/generic filenames
53 descriptive
0 hash-based
1 generic
54 total
FilenameQualityAltIssues
804d6c72010595c9f902e06f0b79497f0326f73a-24x24.svggeneric1
Current: 804d6c72010595c9f902e06f0b79497f0326f73a-24x24.svg
Suggested: production.svg

See Accessibility tab for detailed alt text quality analysis.

A+
Schema Markup Audit
2 schema types detected
PASS

Rich result eligibility

Organization Eligible

Organization knowledge panel

WebSite Eligible

Sitelinks search box

Detected schema types

Organization json-ld → Organization knowledge panel
2/2 required · 3/4 recommended
Required fields (Google)
  • name — Required for the knowledge panel
  • url — Required for entity matching
Recommended fields
  • logo — Strongly recommended — appears in the knowledge panel header
  • sameAs — 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
WebSite json-ld → Sitelinks search box
2/2 required · 0/1 recommended
Required fields (Google)
  • name — Required for the sitelinks search box
  • url — Required to anchor the search box to your domain
Recommended fields
  • potentialAction — Add a SearchAction with target and query-input Enables the in-SERP search box
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

Adding these recommended fields improves chances of getting Sitelinks search box 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