SEO report for telegram.org
https://telegram.org/ · checked Sun, 01 Nov 2026 17:08 GMT
Fix these first
- H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- Meta descriptionhigh
No meta description – Google will pick text from the page.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- Title tagcritical
“Telegram Messenger”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- www / non-wwwmedium
Both www.telegram.org and telegram.org load without redirecting – Google may see duplicate sites.
Fix: Pick one version (with or without www) and 301-redirect the other to it.
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 telegram.org…
Indexing & crawling 60%
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
No robots.txt found (HTTP 404) – crawlers may read everything.
Googlebot is allowed to crawl this page.
Fix: Add a robots.txt that allows crawling and lists your sitemap.
- ✗
XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- ✗
Canonical URLhigh
No canonical tag.
Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.
- ✓
Redirectshigh
1 redirect before the page loaded.
https://telegram.me/ → https://telegram.org/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✗
www / non-wwwmedium
Both www.telegram.org and telegram.org load without redirecting – Google may see duplicate sites.
Fix: Pick one version (with or without www) and 301-redirect the other to it.
Search snippet & sharing 46%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Telegram Messenger”
About 189px of Google's ~580px desktop width – short; use the space.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- ✗
Meta descriptionhigh
No meta description – Google will pick text from the page.
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
No lang attribute on <html>.
Fix: Add lang="en-GB" (or your language) to the <html> tag.
Content quality 38%
Is there enough clear, useful text that matches what the page targets?
- !
Word countmedium
300 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.
- i
Readabilitymedium
Not enough paragraph text to score readability.
- ✓
Topic focushigh
1 of 1 title keywords appear in the main content.
- ✗
H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- ✗
Heading structuremedium
23 headings for 300 words – a lot for the amount of text.
1 skipped level(s), e.g. H2 → H4.
1 empty heading(s).
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✓
Text-to-code ratiolow
10% of the HTML is visible text.
AI search readiness 50%
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. “Why Telegram?”.
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
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
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 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 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 75%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
48 internal and 12 external links.
- ✗
Anchor text qualitymedium
No link text points to two different pages.
1 link(s) with no text at all.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 73%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
708 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
19 kB of HTML.
- ✓
Compressionmedium
Compressed with gzip.
- !
Render-blocking resourceshigh
0 blocking script(s) and 3 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✓
Scripts & third partiesmedium
4 script tag(s); files loaded from 0 other domain(s).
- ✗
Imagesmedium
11 image(s).
11 without width/height – can cause layout shift (CLS).
8 image(s) after the first three aren't lazy-loaded.
0 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: no-store
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 92%
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=31536000; includeSubDomains; preload
- ✗
Security headerslow
Present: clickjacking protection.
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 50%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1.0
- ✗
Image alt textmedium
11 of 11 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✗
Link nameslow
1 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✗
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.