Skip to content

vesremont.com

Record oCnDvx0u9 · Sep 26, 2026

for “bitrix”

This audit was run before live answers existed, so it has no observed verdict.

52/100 readiness

Readiness needs work

How ready the page is to be cited, across 47 signals. Readiness, not a citation count.

Comparison not run. This audit ran without any competing pages to compare against, so there is no ranking to show.

The live answer

No live answer for this audit

This audit doesn't include a live answer from Claude. The score, comparison and fixes below are complete.

Run a fresh audit

How your page compares

No comparison pages were available for this audit.

Readiness, signal by signal

47 signals, each measured from the page itself: 27 pass, 2 weak, 18 missing. Open any signal for the detail and the fix. Every signal is documented in the rubric.

Structure

87/100
  • JSON-LD structured data100

    6 JSON-LD blocks found.

  • JSON-LD validity100

    6 of 6 JSON-LD blocks parse cleanly.

  • Schema type matches query intent100

    Schema types include a informational-intent type (FAQPage).

  • FAQ / Q&A schema100

    FAQPage / QAPage schema present: directly cited by AI Overviews and Perplexity.

  • H1 quality100

    H1: "Товары для дома, ремонта, строительства и профессиональных з…" (64 chars).

  • H2 subtopic coverage75

    3 H2 headings: answer engines decompose a buyer query into subtopics and match each to an H2.

  • Lists (bulleted / numbered)70

    2 lists found.

  • Comparison tables50

    No tables. Comparison / specification tables are heavily cited for product and technical queries.

  • Image alt-text coverage100

    48 of 48 images have alt text (100%).

  • Open Graph metadata100

    Open Graph title, description, and image all present.

  • Internal linking quality56

    142 internal links (94 with descriptive anchors), 0 external.

    Fix: Rewrite generic anchor text ("click here", "read more") to descriptive phrases that include the target page's topic: anchors are direct citation context.

  • Page weight + render-blocking79

    385 KB HTML, 0 blocking script(s), 0 blocking stylesheet(s), 3/48 images without lazy-load.

  • GEO-SFE structural depth (macro/meso/micro)86

    Macro: max heading depth H3 (H1=1, H2=3, H3=7, H4=0). Meso: 5.4 chunks/section avg. Micro: 0.18% visual emphasis.

Authority

49/100
  • Outbound links to authoritative sources0

    0 links to authoritative domains (.edu, .gov, named sources).

    Fix: Add 2-3 outbound citations to .edu / .gov / known publishers. The GEO paper measured this as the #2 citation-lift factor.

  • Inline citations and attributions0

    0 bracketed citations + 0 attribution phrases (per 200 words: 0%).

    Fix: Add inline citations ([1], [2]) or attribution phrases ("according to X"). GEO factor #1 for credibility-weighted citation.

  • Statistic density100

    229 numerical facts (~18.6 per 100 words).

  • Expert quotations0

    0 blockquotes + 0 long inline quotes.

    Fix: Include at least one direct quote from a named expert, ideally in a <blockquote>. Quote-rich pages are 28% more likely to be cited (GEO paper).

  • Author byline0

    No author byline. E-E-A-T penalises anonymous content.

    Fix: Add a visible author byline (a `<div class="byline">` or `[rel="author"]`) AND a `<meta name="author">` tag.

  • Publish + update date markup100

    Both published and modified dates marked up.

  • Content freshness100

    Newest date marker is 0 days old.

  • Technical / domain vocabulary100

    357 multi-syllable words (~29.0% of total).

Content

25/100
  • Direct answer in the lead0

    0 of 1 query terms appear in the first paragraph.

    Fix: Open the page with a direct, complete answer to the buyer query: engines extract their citation snippet from the lead paragraph.

  • Query-term coverage0

    0% of query terms appear somewhere on the page.

    Fix: Cover every term in the buyer query at least once. Missing terms make embeddings drift and competitor pages win retrieval.

  • Named-entity coverage100

    16 distinct proper-noun entities mentioned.

  • Readability (Flesch Reading Ease)20

    Reading-ease score: 162.0 (target 60-70).

    Fix: Page reads too simple: engines down-rank content that lacks domain specificity. Add precise terminology.

  • Content depth100

    1229 words. Target 300-2500: engines bias toward focused depth.

  • Information density100

    Unique-word ratio: 49.6% (target 40-60%).

  • Definitional sentences0

    0 definitional sentences.

    Fix: Include definitional sentences ("X is...", "X refers to..."). Engines specifically extract definitions for AI Overview snippets.

  • BLUF — answer in first 100 words0

    First 100 words cover 0/1 query terms.

    Fix: Put the answer in the FIRST 100 words: Perplexity's pipeline summarizes that exact span before reranking. "BLUF" (bottom-line-up-front) is the format that wins.

  • Mega-page coverage (what/who/how/pricing)0

    0/4 facets covered (what ✗, who ✗, how ✗, pricing ✗).

    Fix: Cover what / who / how / pricing in the same URL. Chatoptic's 75k-page study found the top 4.8% of repeatedly-cited pages share this single-URL completeness.

  • YouTube video presence0

    No YouTube presence.

    Fix: Embed (or link to) a YouTube video covering this topic. Ahrefs's 75k-brand study measured YouTube as the SINGLE strongest correlation (0.737) with AI citation across ChatGPT, AI Mode, and AI Overviews.

  • Sub-query coverage0

    0/3 decomposed sub-questions addressed on the page.

    Fix: Cover the sub-questions buyers actually ask along with the seed query. Currently failing on: what is bitrix · how does bitrix work · bitrix alternatives

Trust

100/100
  • HTTPS100

    Page served over HTTPS.

  • Canonical URL100

    Canonical: https://vesremont.com/

  • Mobile-friendly viewport100

    Viewport meta tag present.

  • Twitter Card100

    Twitter Card metadata present.

  • Meta description100

    Meta description: 162 chars (target 50-160).

  • AI retrieval-bot access (robots.txt)100

    robots.txt allows all AI retrieval bots: your pages are eligible for citation.

  • llms.txt present at /llms.txt100

    /llms.txt found and non-empty: IDE agents (Cursor, Claude Code, Copilot, Windsurf) and Claude.ai will use it for retrieval.

E-E-A-T

22/100
  • First-person language0

    0 first-person pronouns (0.0% of words). Target 0.5-3%.

    Fix: Add first-person language showing lived experience: "we", "our team", "I". Google rates first-person as direct evidence of the new E-for-Experience EEAT pillar.

  • Case study / concrete examples0

    0 case-study patterns matched (examples, results, hands-on phrases).

    Fix: Add at least 2-3 concrete examples or mini-case-studies. "We helped X achieve Y" beats abstract claims; AI engines preferentially cite pages with measurable outcomes.

  • Author bio with credentials0

    No `.author-bio` / `[itemprop="author"]` element found.

    Fix: Add an author-bio section with the author's name, role, and credentials (degree, years of experience, certifications).

  • Byline depth (link + reviewer + date)20

    no linked byline, no reviewer, date ✓

    Fix: Strengthen the byline: link author name to an author profile page; add "reviewed by" / "edited by" markup; mark published + modified dates explicitly.

  • Brand recognized as Wikidata entity0

    No Wikidata entry matched. AI engines preferentially cite brands they recognize as knowledge-graph entities.

    Fix: Create a Wikidata entry for "vesremont" (and a Wikipedia article when notable). The single highest-leverage move for "is this a real, recognized brand?": answer engines key off knowledge graph membership.

  • Press / media mentions0

    0 press-mention pattern(s) matched.

    Fix: Add a "Featured in" / "As seen in" strip listing publications that have covered you. External recognition is a top authority signal.

  • Privacy + Terms links50

    Privacy ✗, Terms ✓.

    Fix: Add Privacy Policy and Terms of Service links (typically in the footer). Their absence is a hard trust-floor signal: Google's quality raters down-rank pages that lack them.

  • Contact information100

    email ✓, phone ✓, address ✓, contact link ✓

The Fix Kit

Readiness needs work (52/100): 7 structural patches needed. Paste-ready patches, filled from what your page already states. Anything in [brackets] is yours to fill in before publishing.

Organization JSON-LD

Schema markup · Medium priority

Organization schema gives the engine an E-E-A-T anchor: pages without one are treated as anonymous.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Vesremont",
  "url": "https://vesremont.com",
  "logo": "https://vesremont.com/logo.png",
  "sameAs": [
    "https://twitter.com/your-handle",
    "https://linkedin.com/company/your-org"
  ]
}
</script>

Internal linking quality

Page structure · Medium priority

142 internal links (94 with descriptive anchors), 0 external.

Rewrite generic anchor text ("click here", "read more") to descriptive phrases that include the target page's topic: anchors are direct citation context.

Outbound links to authoritative sources

Page structure · High priority

0 links to authoritative domains (.edu, .gov, named sources).

Add 2-3 outbound citations to .edu / .gov / known publishers. The GEO paper measured this as the #2 citation-lift factor.

Inline citations and attributions

Page structure · High priority

0 bracketed citations + 0 attribution phrases (per 200 words: 0%).

Add inline citations ([1], [2]) or attribution phrases ("according to X"). GEO factor #1 for credibility-weighted citation.

Expert quotations

Page structure · High priority

0 blockquotes + 0 long inline quotes.

Include at least one direct quote from a named expert, ideally in a <blockquote>. Quote-rich pages are 28% more likely to be cited (GEO paper).

Author byline

Page structure · High priority

No author byline. E-E-A-T penalises anonymous content.

Add a visible author byline (a `<div class="byline">` or `[rel="author"]`) AND a `<meta name="author">` tag.

Direct answer in the lead

Copy · High priority

0 of 1 query terms appear in the first paragraph.

Open the page with a direct, complete answer to the buyer query: engines extract their citation snippet from the lead paragraph.

Rather not ship these yourself?

The Digiocular team can make the changes and check the answer again with you.

See done-for-you

Close the gap, then check again.

The console re-checks the questions you track on a schedule, keeps the history, and tells you whether a fix moved the answer. Or run another free check now.

Re-check schedule

  1. Checked:52/100 readiness
  2. OpenRe-check after you ship the fixes

Audit by VectorCite · vectorcite.digiocular.com