geopus.com
https://geopus.com/yontem
Scanned on August 4, 2026
Quick Wins — Top 5 Issues to Fix
- ✗Title-H1 alignment: 0% word overlap — title and H1 should share key termscontent
- ✗No external links — consider linking to authoritative sourcescontent
- ✗No hreflang tags — add if targeting multiple languagestechnical
- ✗1 render-blocking scripts — add defer or async attributeperformance
- ✗No Strict-Transport-Security headersecurity
SEO — 83/100 (21 issues)
Failed Checks (21)
- ✗Title-H1 alignment: 0% word overlap — title and H1 should share key termscontent
- ✗No external links — consider linking to authoritative sourcescontent
- ✗No hreflang tags — add if targeting multiple languagestechnical
- ✗1 render-blocking scripts — add defer or async attributeperformance
- ✗No Strict-Transport-Security headersecurity
- ✗No Content-Security-Policy header — XSS risksecurity
- ✗No About page link detected — add for credibilitytrust
- ✗No Terms of Service link — add for legal compliance and trusttrust
- ✗No author byline — add "By [Name]" for E-E-A-T trusttrust
- ✗URL lacks title keywords — use a descriptive URL slugtechnical
- ✗No Web App Manifest — add for installability and modern web signalstechnical
- ✗No dns-prefetch or preconnect hints — add for faster third-party loadingperformance
- ✗4% sentences use transition words — aim for 20%+content
- ✗No max-image-preview:large — add to robots meta for Google Discovermeta
- ✗Organization schema missing logo — add for knowledge panelschema
- ✗Missing X-Frame-Options — clickjacking risksecurity
- ✗No Permissions-Policy — restrict camera/mic/geo accesssecurity
- ✗1 paragraph(s) exceed 150 words — break up for readabilitycontent
- ✗2 duplicate ID(s) found: "gp" (2x), "gp-form" (2x) — must be unique per HTML specaccessibility
- ✗No RSS/Atom feed in <head> — add for content discovery by aggregators and AItechnical
- ✗1 of 5 H2 sections have < 50 words — add more content or merge thin sectionscontent
Passed Checks (79)
- ✓Title tag found: "Yöntem ve sınırlar: ne ölçülür, ne ölçülemez — Geopus"meta
- ✓Title length: 53 characters (optimal)meta
- ✓Meta description found (152 chars)meta
- ✓Description length: 152 chars (optimal)meta
- ✓Viewport meta tag found (mobile-friendly)meta
- ✓UTF-8 charset declaredmeta
- ✓Language attribute set on HTML tagmeta
- ✓No meta refresh redirect (good)meta
- ✓No robots meta tag (default: index, follow)meta
- ✓Single H1 tag foundcontent
- ✓5 H2 tags foundcontent
- ✓Heading hierarchy is correctcontent
- ✓703 words on page (good content depth)content
- ✓Readability: 60 (easy to read)content
- ✓9% long sentences (>20 words) — good readabilitycontent
- ✓No images found on pagecontent
- ✓No images to check for dimensionscontent
- ✓No below-fold images to lazy loadcontent
- ✓23 internal links foundcontent
- ✓No empty href attributes foundcontent
- ✓All link texts are descriptive (no "click here" or "read more")content
- ✓Open Graph title foundsocial
- ✓Open Graph description foundsocial
- ✓Open Graph image foundsocial
- ✓Open Graph URL foundsocial
- ✓og:type set to "website"social
- ✓og:site_name: "Geopus"social
- ✓Twitter Card: "summary_large_image"social
- ✓Twitter title foundsocial
- ✓Twitter description foundsocial
- ✓Twitter image foundsocial
- ✓HTTPS enabledtechnical
- ✓Canonical tag foundtechnical
- ✓Canonical points to different URL: https://geopus.com/yontem.html — verify this is intentionaltechnical
- ✓Favicon foundtechnical
- ✓Compression: enabled (vary: accept-encoding)technical
- ✓URL length: 25 chars (good)technical
- ✓URL uses hyphens or no separators (good)technical
- ✓URL is lowercase (good)technical
- ✓No deprecated HTML tags foundtechnical
- ✓Text-to-HTML ratio: 25.9% (good)technical
- ✓Inline CSS: 1.9 KB (acceptable)performance
- ✓Inline JS: 1.7 KB (acceptable)performance
- ✓Font preload/preconnect found — faster font loadingperformance
- ✓Cache-Control: public, max-age=0, must-revalidateperformance
- ✓X-Content-Type-Options: nosniffsecurity
- ✓Contact page/email link foundtrust
- ✓Privacy Policy link foundtrust
- ✓1 JSON-LD schema block(s) foundschema
- ✓Schema types: Organization, Service, WebPageschema
- ✓<!DOCTYPE html> declaredtechnical
- ✓No mixed content — all resources use HTTPStechnical
- ✓All 1 JSON-LD block(s) have valid syntaxschema
- ✓Self-hosted fonts via preload — font-display strategy assumed (not directly verifiable from HTML)performance
- ✓Viewport includes width=device-width (responsive)meta
- ✓robots.txt found and allows crawlingtechnical
- ✓robots.txt includes Sitemap referencetechnical
- ✓No AI crawlers blocked in robots.txt — AI search and training can access contenttechnical
- ✓sitemap.xml found with valid formattechnical
- ✓Sitemap contains 12 URL(s)technical
- ✓All 5 checked internal links are workingcontent
- ✓0% nofollow links (0/23) — good link equity flowcontent
- ✓OG image uses absolute URL (correct)social
- ✓All schema types have required propertiesschema
- ✓Referrer-Policy: strict-origin-when-cross-originsecurity
- ✓H1 length: 27 characters (optimal)content
- ✓Title and meta description are different (good)meta
- ✓OG URL matches canonical URL (consistent)social
- ✓Viewport allows zoom (good for accessibility)accessibility
- ✓26 links on page (within limit)content
- ✓DOM size: ~257 elements (good)performance
- ✓No snippet blocking detected (good — content is fully accessible)technical
- ✓Trailing slash consistent between URL and canonicaltechnical
- ✓Schema dates consistent: published 2026-08-03, modified 2026-08-05schema
- ✓No render-blocking scripts in head (good)performance
- ✓0 third-party script domain(s) (acceptable)performance
- ✓ARIA landmarks present: main, navaccessibility
- ✓All 2 form input(s) have labels or aria-labelsaccessibility
- ✓No iframes on pagesecurity
AEO — 64/100 (17 issues)
Failed Checks (16)
- ✗No definition lists (<dl>) — great for term/value pairsdiscoverability
- ✗No FAQ/Q&A section found — Q&A content helps AI extraction (FAQ schema markup is optional since Google retired FAQ rich results in May 2026)structure
- ✗Few or no lists — add bullet/numbered lists for better AI parsingstructure
- ✗No data tables — tables help AI compare and cite datastructure
- ✗No numbered steps or ordered lists — add for "how to" AI answersstructure
- ✗Few key-value patterns — use "**Label:** value" format for AIstructure
- ✗No author information — AI values attributed contentcitation
- ✗No source citations — reference studies and data for authoritycitation
- ✗Few external links — cite authoritative sources for AI trustcitation
- ✗Formal tone — use more "you", "your", "we" for AI readabilityvoice
- ✗First paragraph too short for AI snippetsvoice
- ✗Content not updated in 90+ days — stale content loses AI visibilitycitation
- ✗No Table of Contents — add jump links for AI content navigationstructure
- ✗No video content — multimedia increases AI engagement and citation ratediscoverability
- ✗Statistics lack source references — attribute data to boost AI trustcitation
- ✗No <details>/<summary> elements — use for expandable Q&A contentstructure
Passed Checks (28)
- ✓Structured data found — AI can understand your contentdiscoverability
- ✓703 words in HTML — good content for AI parsingdiscoverability
- ✓Clean URL structurediscoverability
- ✓5 semantic HTML5 elements founddiscoverability
- ✓4 content sections — well-structured for AIdiscoverability
- ✓Description + OG description both present — clear topic signalsdiscoverability
- ✓6 named entities found — helps AI understand contextdiscoverability
- ✓23 internal links — good topic cluster signaldiscoverability
- ✓Question-style headings found — ideal for AI snippetsstructure
- ✓Concise answer paragraphs after headings — great for AI citationstructure
- ✓91% short sentences — easy for AI to extractstructure
- ✓91% concise paragraphs — scannable for AIstructure
- ✓Avg 143 words/section — sufficient depthstructure
- ✓Publication/modification date foundcitation
- ✓Statistics and data found in content — highly citablecitation
- ✓Organization schema found — AI can identify your brandcitation
- ✓3/5 E-E-A-T signals presentcitation
- ✓Content references 2026/2025 — fresh contentcitation
- ✓Topic focus: 100% — title keywords found in contentcitation
- ✓6 answer-box-ready paragraphs found after headingscitation
- ✓Avg 14 words/sentence — easy reading levelvoice
- ✓Summary/conclusion section found — AI can extract key pointsvoice
- ✓13 H2/H3 headings — good content structure for AIvoice
- ✓2 Q&A blocks — perfect format for AI extractionvoice
- ✓No AI-blocking robots directives — AI crawlers can access contentdiscoverability
- ✓Freshness signal found (Last-Modified header or dateModified)citation
- ✓AI search crawlers not blocked in robots.txt (8/8 allowed)discoverability
- ✓Brand "Geopus" used consistently (6 mentions)citation
GEO — 60/100 (25 issues)
Failed Checks (25)
- ✗Content may be too thin for AI Overview (703 words, 5 sections)overview
- ✗Title and H1 don't align — confusing for AI topic matchingoverview
- ✗No step-by-step content — add numbered guides for AIoverview
- ✗50% optimal paragraphs — aim for 20-80 words per paragraphoverview
- ✗No author schema — add for AI trust signalsauthority
- ✗Only 0/5 trust signals — add reviews, certificationsauthority
- ✗No original data signals — "our research shows..." boosts AI citationauthority
- ✗No expert quotes — add professional opinions for credibilityauthority
- ✗Few industry terms — use relevant jargon for topical authorityauthority
- ✗No links to authoritative sources — cite Google, Schema.org, etc.authority
- ✗Few external source domains — diversify your referencesauthority
- ✗No images — add visuals with descriptive ALT textformat
- ✗No BreadcrumbList schema — add for better AI contextformat
- ✗No lists found — add lists for structured contentformat
- ✗Only 1/6 formatting types — use bold, lists, tables, quotes, codeformat
- ✗Single-perspective content — add "on the other hand..." for balanceformat
- ✗No actionable content — add "you should...", "try...", tipsformat
- ✗No categorization signals — add breadcrumbs or category labelssemantic
- ✗Missing definition or list format — combine "X is..." with lists for snippetsoverview
- ✗Only 0 data points — adding statistics measurably boosts generative-engine visibility (GEO study, arXiv:2311.09735)authority
- ✗Author lacks credentials — anonymous content is a GEO penaltyauthority
- ✗Only 2/6 question types — add What, Why, How headingsoverview
- ✗No authoritative sameAs links — add Wikipedia/Wikidata/LinkedIn URIs to schema for entity disambiguationauthority
- ✗Possible keyword stuffing: "lçüm" at 4.1% density (20×) — diversify vocabularyauthority
- ✗High boilerplate ratio (~49% nav/footer/header) — thin main content for AI extractionoverview
Passed Checks (32)
- ✓Definition-style content found — featured snippet candidateoverview
- ✓2 question headings — matches "People Also Ask" formatoverview
- ✓Content freshness signals detectedoverview
- ✓2-level heading hierarchy — deep content structureoverview
- ✓Source citations found — increases AI trustauthority
- ✓Brand identity consistent (OG + Schema)authority
- ✓Case study or examples found — AI values concrete examplesauthority
- ✓Comparison content detected — AI loves comparingformat
- ✓Summary/conclusion section foundformat
- ✓Data visualization elements found (tables/charts)format
- ✓Conclusion/recommendation found — helps AI provide answersformat
- ✓1 entity types in Schema — AI can classify contentsemantic
- ✓6/14 semantic HTML5 elements — deep semantic structuresemantic
- ✓<time> element found — machine-readable datessemantic
- ✓100% title keywords in first 200 words — good prominencesemantic
- ✓18 contextual links — good cross-referencingsemantic
- ✓2 sections have subtopics (H3) — deep coveragesemantic
- ✓Mobile-friendly (viewport set)technical
- ✓HTTPS secure — trusted by AI systemstechnical
- ✓Page size: 19 KB — reasonabletechnical
- ✓Open Graph fully configured (title, description, image)technical
- ✓Canonical URL set — prevents AI from citing duplicatestechnical
- ✓Page allows AI indexing (no noindex/nosnippet)technical
- ✓3 Schema types — rich structured datatechnical
- ✓Language + OG locale set — clear language signaltechnical
- ✓3 ARIA landmarks found — good accessibility for AItechnical
- ✓703 words — sufficient depth for AI analysisoverview
- ✓First 200 words contain topic keywords — AI extracts primarily from the startoverview
- ✓No snippet restrictions — AI can freely extract content (good)technical
- ✓Link anchor texts are descriptive — good AI context signalsemantic
- ✓No hidden-text cloaking patterns detectedtrust
- ✓All tested AI crawlers can access the page (GPTBot, ClaudeBot, PerplexityBot)authority
Fix These Issues Automatically
Using WordPress? Install SEO Autopilot for one-click auto-fixes on 65+ issues — with full undo support.
Get SEO Autopilot Plugin