render.com
Grade B+
Audited Nov 10
49 checks
SEO, GEO and AEO audit · home page score ·
SEO audit for render.com
render.com scored 85 out of 100 (grade B+) in the ratemysite.ai audit of 49 checks across technical SEO, content, answer engines, AI readiness and speed, with 11 issues to fix.
Email me about this score
Compare with another site
Show your score on your site
Audit complete. This site is good
Summary
Site health score
Grade B+85 out of 100

This site is good. 11 things to improve.
First audit of this domain
Technical SEO
100
14 checks · no issues
Content
83
8 checks · 3 warnings
Answer engines
50
9 checks · 2 failed, 5 warnings
AI readiness
98
12 checks · 1 warning
Speed
n/a
6 checks · no issues
Fix first
11 of 43 checksWarning: Direct answer after the H1Answer engines (AEO)
first paragraph after the H1 has 15 words, aim for 25 or more
Medium impactHow to fix: Direct answer after the H1
Failed: FAQ schemaAnswer engines (AEO)
no FAQ section or FAQPage schema
Medium impactHow to fix: FAQ schema
Core Web Vitals
Largest Contentful Paint not measured
Cumulative Layout Shift not measured
Time to First Byte not measured
Site health
The other pages were not scanned in this audit.
AI crawler access
3 of 16 allowedGPTBotPartly blockedOAI-SearchBotPartly blockedChatGPT-UserPartly blockedClaudeBotPartly blockedClaude-SearchBotPartly blockedClaude-UserPartly blocked
Google preview
Desktoprender.com
Render | The cloud for builders
Deploy and scale any app or agent from your first user to your billionth. Build faster on intuitive cloud infrastructure for the modern web.
Every check, by category
Technical SEO
Technical SEO is in great shape
Whether search engines can crawl, index and understand the page: title, meta description, headings, canonical, HTTPS, robots.txt and sitemap.
Passed: Title tag length
title is 31 characters
Passed: Meta description
meta description is 140 characters
Passed: Single H1
exactly one H1
Passed: Heading hierarchy
29 headings in order
Passed: Canonical URL
canonical is self-referencing
Passed: Mobile viewport
viewport: width=device-width, initial-scale=1, maximum-scale=1
Passed: HTML lang attribute
lang="en"
Passed: HTTPS and redirect
https with http redirecting to https
Passed: robots.txt
robots.txt present and allows crawling
Passed: XML sitemap
sitemap.xml reachable
Passed: Indexable (no noindex)
page is indexable
Passed: Image alt text
all 78 images have an alt attribute, 48 decorative (alt="")
Passed: Internal links
93 internal links
Content and E-E-A-T
Content and E-E-A-T is good
Trust and depth signals: a named author, a visible date, contact and privacy pages, enough readable text and sources linked out.
Warning: ReadabilityLow impact
What we found
Flesch reading ease 27, aim for 50 or more
Why it matters
Flesch reading ease is a score from 0 to 100 that rates how easy text is to read. This check scores the whole page: 50 points or more passes, and lower gets a warning.
Warning: Visible dateLow impact
What we found
no visible published or updated date
Why it matters
A visible date is a line that shows when a page was updated. The check passes on a time tag, date meta tag, structured data date, or text like Updated 2026. Otherwise it warns.
Passed: Content length
1176 words of visible text
Passed: Links to sources
8 external domains linked: community.render.com, status.render.com, cdn.sanity.io, dashboard.render.com, docs.render.com, github.com, discord.gg, reddit.com
Passed: Contact or about page
contact or about page linked (/about)
Passed: Privacy policy
privacy policy linked (/privacy)
Passed: Title differs from H1
title "render | the cloud for builders" differs from H1 "your fastest path to production foryour fastest path to production for any workloadany workloadany workloadapps & agentsapps & agentsworkflowsworkflowsapis & web appsapis & web appsdata pipelinesdata pipelineshipaa appshipaa apps"
Keyword consistency
The most used words on the page and where they appear.
| Keyword | Title | Meta description | Headings | On the page |
|---|---|---|---|---|
| render | Yes | No | Yes | 31 |
| services | No | No | Yes | 12 |
| agent | No | Yes | Yes | 9 |
| docs | No | No | No | 8 |
| private | No | No | Yes | 8 |
| build | No | Yes | No | 7 |
| infrastructure | No | Yes | Yes | 7 |
| agents | No | No | Yes | 6 |
| apps | No | No | Yes | 6 |
| code | No | No | Yes | 6 |
Answer engines (AEO)
Answer engines (AEO) has serious issues
How easily answer engines can lift an answer from the page: a direct answer up top, question headings, definitions and structured data.
Warning: Direct answer after the H1Medium impact
What we found
first paragraph after the H1 has 15 words, aim for 25 or more
Why it matters
A direct answer is a short paragraph right under the H1 that answers the page's question. This check fails under 10 words, warns from 10 to 24, and passes at 25 words or more.
Failed: FAQ schemaMedium impact
What we found
no FAQ section or FAQPage schema
Why it matters
FAQPage is a Schema.org type that marks up questions and answers as JSON-LD. This check passes with FAQPage markup, warns on an FAQ heading without it, and fails with neither.
Warning: Data pointsLow impact
What we found
3 data points found (8 million, 100x, $60,000), aim for 5 or more
Why it matters
Data density is a count of the hard facts in your text, such as years, prices and percentages. This check passes at 5 data points, warns at 1 to 4, and fails at 0.
Warning: DefinitionsLow impact
What we found
no definition-style sentence ("X is a ...")
Why it matters
A definition is a sentence that says what a term is, in the form X is a category. This check passes when the page has one and warns when it has none.
Warning: HowTo schemaLow impact
What we found
step list found but no HowTo schema
Why it matters
HowTo is a Schema.org type that marks up the steps of a task. This check applies when a page has a numbered list of 3 or more items, and warns if HowTo markup is missing.
Warning: Question-style headingsLow impact
What we found
no H2 or H3 phrased as a question
Why it matters
A question heading is an H2 or H3 written as the question its section answers. The check passes if one ends in a question mark or starts with a word like how or what.
Passed: Organization and WebSite schema
structured data: organization, website, softwareapplication
Passed: Lists and tables
3 lists, 0 tables in the main content
AI readiness (GEO)
AI readiness (GEO) is in great shape
Whether AI assistants such as ChatGPT, Claude and Perplexity can reach, read and cite the site: crawler access, llms.txt and content that works without JavaScript.
Warning: ai.txtLow impact
What we found
no /.well-known/ai.txt
Why it matters
ai.txt is a plain text file that states how AI systems may use your content. It lives at /.well-known/ai.txt. It is optional and support is uneven, but some crawlers and agents read it.
Passed: llms.txt
/llms.txt with 403 links
Passed: llms-full.txt
/llms-full.txt present
Passed: AI crawler access
all tier 1 and tier 2 AI crawlers allowed
Passed: Content without JavaScript
1176 words available without JavaScript
Passed: Cache headers
Cache-Control "s-maxage=1, stale-while-revalidate=31535999"
Passed: Markdown version
serves text/markdown on request
Passed: Brand name consistency
brand "Render" (from og:site_name) consistent across title, OG and schema
Passed: No paywall or interstitial
no paywall or interstitial detected
Passed: X-Robots-Tag for AI
no AI restriction in X-Robots-Tag
Passed: HTML size
HTML is 743 KB
Passed: Citable entity links
4 sameAs links in structured data: https://twitter.com/render, https://github.com/renderinc, https://www.linkedin.com/company/renderco
Speed
Score not available
How fast the page loads and responds on a phone, from Google PageSpeed and real Chrome user data when Google has it.
Not applicable: Largest Contentful Paint
Largest Contentful Paint not measured
Not applicable: Interaction to Next Paint
Interaction to Next Paint not measured
Not applicable: Cumulative Layout Shift
Cumulative Layout Shift not measured
Not applicable: Time to First Byte
Time to First Byte not measured
Not applicable: Page weight
total page weight not measured
Not applicable: Request count
request count not measured
Site details
Technology
Software and libraries we could identify from the page and its headers.
- Next.js(Framework)
- Google Tag Manager(Analytics and ads)
- Cloudflare(CDN)
- HSTS(Security)
Social
Profiles linked from the page, and tracking pixels.
- FacebookNot linked
- InstagramNot linked
- X (Twitter)x.com/render
- LinkedInlinkedin.com/company/renderco
- YouTubeyoutube.com/@render-inc
- TikTokNot linked
- PinterestNot linked
- Tracking pixelsGoogle Tag Manager
Local SEO
Only matters for businesses with a place customers visit.
- Phone on the pageNot found
- Address on the pageNot found
- LocalBusiness schemaNot found
- Google Maps or Business Profile linkNot found
Site insights
What we found on the page beyond the checks. None of it changes the score.
AI crawler access
Which AI crawlers your robots.txt lets in, and the rule that decides.
3 of 16 allowed, 0 blocked, 13 partly blocked
GPTBotOpenAIPartly blockedCollects content to train OpenAI models
Disallow: /contact-salesOAI-SearchBotOpenAIPartly blockedIndexes pages for ChatGPT search answers
Disallow: /contact-salesChatGPT-UserOpenAIPartly blockedFetches a page when a ChatGPT user asks for it
Disallow: /contact-salesClaudeBotAnthropicPartly blockedCollects content to train Claude models
Disallow: /contact-salesClaude-SearchBotAnthropicPartly blockedIndexes pages for Claude search answers
Disallow: /contact-salesClaude-UserAnthropicPartly blockedFetches a page when a Claude user asks for it
Disallow: /contact-salesPerplexityBotPerplexityPartly blockedIndexes pages for Perplexity answers
Disallow: /contact-salesPerplexity-UserPerplexityAllowedFetches a page when a Perplexity user asks for it
Allow: /(applies to all crawlers)Google-ExtendedGooglePartly blockedA control token, not a crawler: tells Google whether Gemini may use your content
Disallow: /contact-salesApplebot-ExtendedApplePartly blockedA control token, not a crawler: tells Apple whether its AI models may use your content
Disallow: /contact-salesAmazonbotAmazonPartly blockedIndexes pages for Alexa and Amazon answers
Disallow: /contact-salesmeta-externalagentMetaPartly blockedCollects content for Meta AI
Disallow: /contact-salesCCBotCommon CrawlPartly blockedBuilds the open web dataset many AI models train on
Disallow: /contact-salesBytespiderByteDancePartly blockedCollects content for ByteDance AI models
Disallow: /contact-salesDuckAssistBotDuckDuckGoAllowedFetches pages for DuckDuckGo AI answers
Allow: /(applies to all crawlers)MistralAI-UserMistralAllowedFetches a page when a Le Chat user asks for it
Allow: /(applies to all crawlers)
ChatGPT-User, Claude-User, Perplexity-User and MistralAI-User fetch pages when a person asks, and may not follow robots.txt rules.
Google search preview
An approximate preview of how this page can look in Google results.
render.com
Render | The cloud for builders
Deploy and scale any app or agent from your first user to your billionth. Build faster on intuitive cloud infrastructure for the modern web.
render.com
Render | The cloud for builders
Deploy and scale any app or agent from your first user to your billionth. Build faster on intuitive cloud infrastructure for the modern web.
Google PageSpeed
Google's lab test of this page on a phone and on a desktop.
| Metric | Phone | Desktop |
|---|---|---|
| Google score | n/a | 55 |
| First Contentful Paint | n/a | 477 ms |
| Speed Index | n/a | 2.8 s |
| Largest Contentful Paint | n/a | 2.0 s |
| Time to Interactive | n/a | 4.9 s |
| Total Blocking Time | n/a | 1.1 s |
| Cumulative Layout Shift | n/a | 0.01 |
Desktop opportunities
- Reduce JavaScript execution time2.6 s, saves about 1.1 s
- Minimize main-thread work5.4 s, saves about 1.1 s
- Render-blocking requestsEst savings of 170 ms
- Use efficient cache lifetimesEst savings of 588 KiB, saves about 100 ms
- Reduce unused JavaScriptEst savings of 475 KiB, saves about 100 ms
- Reduce unused CSSEst savings of 41 KiB, saves about 50 ms
- Duplicated JavaScriptEst savings of 16 KiB
- Improve image deliveryEst savings of 98 KiB
Page weight (desktop)
| Type | Requests | Size |
|---|---|---|
| Total | 159 | 3.8 MB |
| Script | 74 | 1.6 MB |
| Image | 31 | 1.2 MB |
| Font | 11 | 629 KB |
| Other | 36 | 264 KB |
| Document | 1 | 175 KB |
| Stylesheet | 6 | 63 KB |
JavaScript errors (desktop)
4 errors in the browser console.
- javascript: Access to XMLHttpRequest at 'https://consent.api.osano.com/record' from origin 'https://render.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No
- network: Failed to load resource: net::ERR_FAILED
- security: Loading the script 'https://bzrcdn.openai.com/sdk/oaiq.min.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.osano.com https://*.
- security: Loading the script 'https://static.ads-twitter.com/uwt.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.osano.com https://*.post
Headings
H1 1, H2 6, H3 22
- H1Your fastest path to production forYour fastest path to production for any workloadany workloadany workloadapps & agents
- H2Click, click, done.Click, click, done.
- H3Create a service
- H3Push your code
- H3Render does the rest
- H2Whatever your stack, it runs on Render
- H2Deploy app and agent workloads with zero opsDeploy app and agent workloads with zero ops
- H3Full-stack previews for every pull request
- H3Load-based autoscaling that handles 100x traffic bursts and beyond
- H3Integrated logs and monitoring for builds, deploys and live services
- H3Durable, highly-parallel workflows as code
- H3Isolated, fast-starting sandboxes for agents
- H2Intuitive infrastructure, designed for buildersIntuitive infrastructure, designed for builders
- H3Native language runtimes
- H3Infrastructure as code
- H3Isolated environments
- H3Object storage
- H3Redis-compatible Key Value
- H3WebSockets
- H3Edge caching
- H3Fully-managed TLS
- H2Stay secure and resilient by defaultStay secure and resilient by default
- H3Private networking
- H3Built-in DDoS protection
- H3Managed compliance
- H3Audit controls
- H3Encryption at rest
- H3Unique user identification
- H2Start building with RenderStart building with Render
Links on this page
119 links: 93 internal, 26 external, 0 nofollow.
- Learn more https://render.com/sandboxesVague link text
- https://render.com/No link text
Email security
SPF and DMARC records stop others from sending email that pretends to come from this domain.
- SPFFound: other servers are marked as suspicious (soft fail)
v=spf1 include:_spf.google.com include:stspg-customer.com include:_spf.salesforce.com include:21532664.spf10.hubspotemail.net ~all - DMARCFound: fake emails are rejected
v=DMARC1; p=reject; sp=reject; rua=mailto:re+m3u79gyogz8@inbound.dmarcdigests.com; aspf=r; pct=100;at _dmarc.render.com
Score history
The overall score of each audit of this site, oldest first.
First audit of this domain
Questions about this report
What is the SEO score of render.com?
render.com scored 85 out of 100, grade B+, with technical SEO 100, content 83, answer engines 50, AI readiness 98 and speed not scored.
What should render.com fix first?
Start with Direct answer after the H1: first paragraph after the H1 has 15 words, aim for 25 or more. This report has 11 issues to fix in total.
How is the site health score calculated?
Site health is a score from 0 to 100 that combines five category scores. Technical SEO counts for 25%, content counts for 15%, answer engines counts for 20%, AI readiness counts for 25% and speed counts for 15%.
How often can this report be updated?
A new audit can run 24 hours after the last one. To run it, use the Re-analyze button at the top of this page.
Is this audit free?
Yes. Audits are free and need no account.