SEO report for prlog.ru
https://prlog.ru/ · checked Sun, 01 Nov 2026 14:05 GMT
Fix these first
- Mobile viewportcritical
No viewport meta tag – the page won't fit phones.
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
- 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.
- 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
“Анализ сайта, проверка тИЦ и PR. Позиции в Яндексе и Google”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- H1 headingcritical
“PRLOG”
Fix: Use one H1 that states the page topic with its main keyword.
- Open Graph & social cardsmedium
Open Graph title or image missing.
Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.
- Question-led contentmedium
No headings phrased as questions.
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.
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 prlog.ru…
Indexing & crawling 88%
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
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
Canonical: https://prlog.ru/
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.prlog.ru redirects to prlog.ru.
Search snippet & sharing 33%
How the page looks in Google results and when shared.
- !
Title tagcritical
“Анализ сайта, проверка тИЦ и PR. Позиции в Яндексе и Google”
About 593px of Google's ~580px desktop width – it will probably be cut off.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
142 characters, ~997px 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
No favicon linked.
Fix: Add a square favicon at least 48×48px.
- ✗
Languagelow
No lang attribute on <html>.
Fix: Add lang="en-GB" (or your language) to the <html> tag.
Content quality 54%
Is there enough clear, useful text that matches what the page targets?
- !
Word countmedium
219 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
5 of 7 title keywords appear in the main content (missing: позиции, яндексе).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- !
H1 headingcritical
“PRLOG”
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
17 headings for 219 words – a lot for the amount of text.
1 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✓
Text-to-code ratiolow
20% of the HTML is visible text.
AI search readiness 38%
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
No headings phrased as questions.
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 contact; missing about and privacy.
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 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
39 internal and 0 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 92%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
89 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
9 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 0 stylesheet(s) in <head>.
- ✓
Scripts & third partiesmedium
7 script tag(s); files loaded from 2 other domain(s): mc.yandex.ru, ajax.googleapis.com.
- ✓
Imagesmedium
No <img> tags.
- ✗
Cachinglow
No Cache-Control header.
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 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 25%
Usable on phones and by everyone – Google indexes the mobile version.
- ✗
Mobile viewportcritical
No viewport meta tag – the page won't fit phones.
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
- ✓
Image alt textmedium
No images.
- ✗
Form labelsmedium
1 of 1 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- ✓
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.