SEO report for remoteleverage.com
https://remoteleverage.com/ · checked Wed, 11 Nov 2026 19:32 GMT
Fix these first
- Title tagcritical
“Hire Remote Talent from LATAM | Remote Leverage”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- Imagesmedium
77 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
- Heading structuremedium
40 headings for 1491 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- Text-to-code ratiolow
4% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
- llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- Trust pages (E-E-A-T)medium
Links found to about and privacy; missing contact.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to remoteleverage.com…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap index found at https://remoteleverage.com/sitemap_index.xml listing 7 sitemaps.
Declared in robots.txt.
Most recent lastmod: 2026-11-09T17:21:43+00:00.
- ✓
Canonical URLhigh
Canonical: https://remoteleverage.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.remoteleverage.com redirects to remoteleverage.com.
Search snippet & sharing 79%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Hire Remote Talent from LATAM | Remote Leverage”
About 466px of Google's ~580px desktop width.
Repeated words: remote.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- ✓
Meta descriptionhigh
137 characters, ~879px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-US"
Content quality 87%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,491 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✓
Readabilitymedium
Flesch reading ease 65 (plain English), about 11 words per sentence.
- ✓
Topic focushigh
5 of 5 title keywords appear in the main content.
- ✓
H1 headingcritical
“Latin American Remote Talent $6-$10 Per Hour”
- !
Heading structuremedium
40 headings for 1491 words – a lot for the amount of text.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
4% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 88%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✓
Question-led contentmedium
4 heading(s) phrased as questions, e.g. “Why Remote Leverage”.
- ✓
Entity clarityhigh
Identified as: Organization.
5 official profile link(s) (sameAs).
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- !
Trust pages (E-E-A-T)medium
Links found to about and privacy; missing contact.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
2 JSON-LD block(s): WebPage, ReadAction, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization, ImageObject, FAQPage, Question.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
76 internal and 1 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 75%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
97 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- !
HTML sizemedium
246 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 1 stylesheet(s) in <head>.
- !
Scripts & third partiesmedium
16 script tag(s); files loaded from 1 other domain(s): facebook.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
77 image(s).
3 without width/height – can cause layout shift (CLS).
5 image(s) after the first three aren't lazy-loaded.
67 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✓
Cachinglow
Cache-Control: public, s-maxage=60, stale-while-revalidate=600, stale-if-error=86400
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 75%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: none.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 77 images have alt text.
- ✓
Form labelsmedium
All 12 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.