SEO report for codingteam.ru

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 codingteam.ru…

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://codingteam.ru/sitemap.xml with 125 URLs.

  Declared in robots.txt.

  This page is listed in it.

  No lastmod dates – add accurate ones so search engines know what changed.

• ✓

  Canonical URLhigh

  Canonical: https://codingteam.ru/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.codingteam.ru isn't in use (HTTP 526).

Search snippet & sharing 46%

How the page looks in Google results and when shared.

• ✗

  Title tagcritical

  “Разработка программного обеспечения (ПО) на заказ от компании Coding Team”

  About 756px 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.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  241 characters, ~1732px 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.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary_large_image.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="ru"

Content quality 58%

Is there enough clear, useful text that matches what the page targets?

• !

  Word countmedium

  324 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.

  Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.

  Count words and keywords with the free word counter

  Read the guide: how to write SEO content

• i

  Readabilitymedium

  Reading-ease scores only work for English; this page is lang="ru".

• !

  Topic focushigh

  4 of 7 title keywords appear in the main content (missing: заказ, coding, team).

  Fix: Use your main title phrases naturally in the opening paragraph and headings.

  Find the phrases people search with the free keyword generator

  Read the guide: how to write SEO content

• ✓

  H1 headingcritical

  “Разработка программного обеспечения”

• ✗

  Heading structuremedium

  23 headings for 324 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.

  Read the guide: the on-page SEO checklist

• ✗

  Text-to-code ratiolow

  1% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 44%

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

  /llms.txt found.

• ✗

  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.

  Read the guide: how to write SEO content

• ✗

  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.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✗

  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 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  3 JSON-LD block(s): SiteNavigationElement, WebPage, BreadcrumbList, ListItem.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  40 internal and 12 external links.

• ✗

  Anchor text qualitymedium

  No link text points to two different pages.

  4 link(s) with no text at all.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

Performance 43%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• !

  Server response (TTFB)high

  985 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

• !

  HTML sizemedium

  387 kB of HTML.

  Fix: Remove inline bloat, base64 images and unused markup.

• ✓

  Compressionmedium

  Compressed with gzip.

• ✗

  Render-blocking resourceshigh

  1 blocking script(s) and 20 stylesheet(s) in <head>.

  Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  Read the guide: Core Web Vitals

• ✗

  Scripts & third partiesmedium

  55 script tag(s); files loaded from 1 other domain(s): mc.yandex.ru.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• !

  Imagesmedium

  42 image(s).

  All images reserve their space.

  6 image(s) after the first three aren't lazy-loaded.

  The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.

  40 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.

  Read the guide: image SEO

• ✓

  Cachinglow

  Cache-Control: s-maxage=900, stale-while-revalidate=31535100

• 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 67%

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.

  Read the guide: the technical SEO checklist

• ✗

  Security headerslow

  Present: none.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✗

  Server fingerprintlow

  X-Powered-By reveals “Next.js”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 90%

Usable on phones and by everyone – Google indexes the mobile version.

• ✓

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1

• ✓

  Image alt textmedium

  All 42 images have alt text.

• ✗

  Link nameslow

  4 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✓

  Tap-to-contactmedium

  One-tap contact: phone and email.

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  No postcode found (fine for service-area businesses).

  An email link is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist