SEO report for feedly.com
https://feedly.com/ · checked Sun, 01 Nov 2026 16:04 GMT
Fix these first
- Title tagcritical
“Feedly Threat Intelligence: Collect, analyze, and share actionable intelligence”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Trust pages (E-E-A-T)medium
Links found to privacy; missing about and 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.
- 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.
- Meta descriptionhigh
172 characters, ~1013px of ~990px.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- Readabilitymedium
Flesch reading ease 46 (fairly difficult), about 10 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- Heading structuremedium
23 headings for 471 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.
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 feedly.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 found at https://feedly.com/sitemap.xml with 3,970 URLs.
Declared in robots.txt.
This page is NOT listed in it.
Most recent lastmod: 2026-11-01.
- ✓
Canonical URLhigh
Canonical: https://feedly.com/
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.feedly.com redirects to feedly.com.
Search snippet & sharing 46%
How the page looks in Google results and when shared.
- ✗
Title tagcritical
“Feedly Threat Intelligence: Collect, analyze, and share actionable intelligence”
About 685px of Google's ~580px desktop width – it will probably be cut off.
Repeated words: intelligence.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
172 characters, ~1013px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 80%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
471 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 46 (fairly difficult), about 10 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
5 of 6 title keywords appear in the main content (missing: share).
- ✓
H1 headingcritical
“The fastest way to track emerging threats with AI”
- !
Heading structuremedium
23 headings for 471 words – a lot for the amount of text.
2 skipped level(s), e.g. H2 → H4.
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 63%
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
1 heading(s) phrased as questions, e.g. “What's new?”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✓
Entity clarityhigh
Identified as: Organization.
2 official profile link(s) (sameAs).
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✗
Trust pages (E-E-A-T)medium
Links found to privacy; missing about and 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): Organization, WebApplication, Offer.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
40 internal and 9 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 88%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
49 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
86 kB of HTML.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 2 stylesheet(s) in <head>.
- !
Scripts & third partiesmedium
12 script tag(s); files loaded from 1 other domain(s): image.mux.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✓
Imagesmedium
34 image(s).
All images reserve their space.
22 use WebP/AVIF or responsive srcset.
- !
Cachinglow
Cache-Control: public, max-age=0, must-revalidate
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 100%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=15552000
- ✓
Security headerslow
Present: CSP, nosniff, Referrer-Policy, Permissions-Policy, clickjacking protection.
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 80%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width
- ✓
Image alt textmedium
All 34 images have alt text.
- ✓
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.