staalshop.no

https://staalshop.no/

Scanned on May 4, 2026

Overall

SEO

72/101 passed

AEO

23/52 passed

GEO

24/58 passed

119

Passed

Failed

211

Total Checks

Poor

Rating

Quick Wins — Top 5 Issues to Fix

✗No theme-color meta tag — improves mobile browser appearancemeta
✗Only 239 words — thin content may rank poorlycontent
✗50% long sentences (>20 words) — break up for readabilitycontent
✗6 images missing width/height — causes layout shift (CLS)content
✗13 of 13 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent

SEO — 71/100 (29 issues)

Failed Checks (29)

✗No theme-color meta tag — improves mobile browser appearancemeta
✗Only 239 words — thin content may rank poorlycontent
✗50% long sentences (>20 words) — break up for readabilitycontent
✗6 images missing width/height — causes layout shift (CLS)content
✗13 of 13 images use legacy formats (JPG/PNG/GIF) — convert to WebP/AVIF for 25-50% smaller filescontent
✗Missing og:image — social shares will lack visualssocial
✗Missing twitter:imagesocial
✗No hreflang tags — add if targeting multiple languagestechnical
✗Text-to-HTML ratio: 3.1% — too code-heavy, add more contenttechnical
✗14 render-blocking scripts — add defer or async attributeperformance
✗No font preload/preconnect — add for faster renderingperformance
✗No Cache-Control header — browser cannot cache effectivelyperformance
✗No Strict-Transport-Security headersecurity
✗Missing X-Content-Type-Options headersecurity
✗No Content-Security-Policy header — XSS risksecurity
✗No About page link detected — add for credibilitytrust
✗No Privacy Policy link — required by GDPR and improves trusttrust
✗No Terms of Service link — add for legal compliance and trusttrust
✗1 HTTP resource(s) on HTTPS page — security risktechnical
✗2 target="_blank" links missing rel="noopener" — security risksecurity
✗No Web App Manifest — add for installability and modern web signalstechnical
✗0% sentences use transition words — aim for 20%+content
✗Only 23% responsive images — add srcset for mobilecontent
✗Missing X-Frame-Options — clickjacking risksecurity
✗No Permissions-Policy — restrict camera/mic/geo accesssecurity
✗1 render-blocking script(s) in head — add defer or asyncperformance
✗1 iframe(s) without sandbox attribute — security risksecurity
✗No IndexNow integration — add for instant Bing/Yandex indexing on content changestechnical
✗4 of 6 H2 sections have < 50 words — add more content or merge thin sectionscontent

Passed Checks (72)

✓Title tag found: "Hjem | Stålshop AS – Leverandør Av Stål Og Metaller"meta
✓Title length: 51 characters (optimal)meta
✓Meta description found (158 chars)meta
✓Description length: 158 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
✓Robots: "follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large"meta
✓Single H1 tag foundcontent
✓Title-H1 alignment: 80% word overlap (good)content
✓6 H2 tags foundcontent
✓Heading hierarchy is correctcontent
✓Readability: 32 (moderate — aim for 60+)content
✓All 13 images have ALT textcontent
✓JS-based lazy loading detectedcontent
✓20 internal links foundcontent
✓1 external 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 URL foundsocial
✓og:type set to "website"social
✓og:site_name: "Stålshop AS – leverandør av Stål og metaller"social
✓Twitter Card: "summary_large_image"social
✓Twitter title foundsocial
✓Twitter description foundsocial
✓HTTPS enabledtechnical
✓Canonical tag foundtechnical
✓Canonical tag is self-referencing (correct)technical
✓Favicon foundtechnical
✓Apple touch icon foundtechnical
✓Compression: gziptechnical
✓URL length: 21 chars (good)technical
✓URL uses hyphens or no separators (good)technical
✓No deprecated HTML tags foundtechnical
✓Inline CSS: 10.3 KB (acceptable)performance
✓Inline JS: 6.1 KB (acceptable)performance
✓Contact page/email link foundtrust
✓Author byline found + author in schematrust
✓1 JSON-LD schema block(s) foundschema
✓Schema types: Organization, WebSite, WebPage, Person, BlogPostingschema
✓<!DOCTYPE html> declaredtechnical
✓All 1 JSON-LD block(s) have valid syntaxschema
✓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 1 URL(s)technical
✓All 5 checked internal links are workingcontent
✓0% nofollow links (0/22) — good link equity flowcontent
✓2 resource hint(s) (dns-prefetch/preconnect) — faster loadingperformance
✓All schema types have required propertiesschema
✓Title uses "|" separator — Google may rewrite it; consider using "—" insteadmeta
✓max-image-preview:large — eligible for Google Discover large imagesmeta
✓Organization schema includes logoschema
✓Referrer-Policy: no-referrer-when-downgradesecurity
✓H1 length: 50 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
✓29 links on page (within limit)content
✓DOM size: ~375 elements (good)performance
✓No snippet blocking detected (good — content is fully accessible)technical
✓Schema dates consistent: published 2020-04-17T07:44:42+02:00, modified 2025-11-13T22:26:10+01:00schema
✓2 third-party script domain(s) (acceptable)performance
✓ARIA landmarks present: main, nav, skip-linkaccessibility
✓All 0 form input(s) have labels or aria-labelsaccessibility
✓No duplicate IDs found (50 unique IDs)accessibility
✓1 feed(s) discovered (RSS) — aids content discoverytechnical

AEO — 44/100 (29 issues)

Failed Checks (29)

✗Only 1 content sections — segment your content betterdiscoverability
✗No definition lists (<dl>) — great for term/value pairsdiscoverability
✗No code blocks — add <code>/<pre> for technical contentdiscoverability
✗No FAQ section found — add Q&A content for AI citationstructure
✗No question-style headings — try "How to...", "What is..."structure
✗No data tables — tables help AI compare and cite datastructure
✗No concise answer paragraphs detected — add short summaries after headingsstructure
✗No numbered steps or ordered lists — add for "how to" AI answersstructure
✗Few key-value patterns — use "**Label:** value" format for AIstructure
✗Avg 39 words/section — expand sections for AI comprehensionstructure
✗No source citations — reference studies and data for authoritycitation
✗Few external links — cite authoritative sources for AI trustcitation
✗No recent year mentioned — AI prefers up-to-date contentcitation
✗Only 0 concise answer paragraph(s) after headings — add 2+ short summaries (40-200 chars) right after H2/H3 tagscitation
✗No Speakable schema — add for voice assistant optimizationvoice
✗Formal tone — use more "you", "your", "we" for AI readabilityvoice
✗First paragraph too short for AI snippetsvoice
✗Avg 25 words/sentence — simplify for AI and voicevoice
✗Pronoun density: 0.0% — add more "you/your" for engagementvoice
✗No summary section — add Key Takeaways for AI extractionvoice
✗Few Q&A blocks — add question headings followed by answer paragraphsvoice
✗No /llms.txt found — add one to guide AI crawlers (emerging standard)discoverability
✗No sameAs links in schema — add social profiles for brand recognitioncitation
✗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
✗Brand name used inconsistently (4 partial vs 2 full) — standardizecitation

Passed Checks (23)

✓Structured data found — AI can understand your contentdiscoverability
✓239 words in HTML — good content for AI parsingdiscoverability
✓Clean URL structurediscoverability
✓4 semantic HTML5 elements founddiscoverability
✓Description + OG description both present — clear topic signalsdiscoverability
✓11 named entities found — helps AI understand contextdiscoverability
✓20 internal links — good topic cluster signaldiscoverability
✓2 lists found — structured content for AIstructure
✓50% short sentences — easy for AI to extractstructure
✓100% concise paragraphs — scannable for AIstructure
✓Author information found — builds E-E-A-Tcitation
✓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
✓Topic focus: 100% — title keywords found in contentcitation
✓SearchAction schema found — sitelinks search box enabledvoice
✓Active voice dominant (0% passive) — AI-friendlyvoice
✓15 H2/H3 headings — good content structure for AIvoice
✓No AI-blocking robots directives — AI crawlers can access contentdiscoverability
✓Freshness signal found (Last-Modified header or dateModified)citation
✓AI crawlers allowed in robots.txt (0/4 explicitly listed)discoverability
✓Brand name consistent across 2/3 signals (title, OG, schema)citation

GEO — 41/100 (34 issues)

Failed Checks (34)

✗No clear definitions — add "X is..." patterns for AI Overviewoverview
✗Few question headings — add Q&A headings for AI Overviewoverview
✗Content may be too thin for AI Overview (239 words, 6 sections)overview
✗No step-by-step content — add numbered guides for AIoverview
✗14% optimal paragraphs — aim for 20-80 words per paragraphoverview
✗No source citations — reference studies and data for authorityauthority
✗Only 1/5 trust signals — add reviews, certificationsauthority
✗No original data signals — "our research shows..." boosts AI citationauthority
✗No expert quotes — add professional opinions for credibilityauthority
✗No examples or case studies — add real-world examplesauthority
✗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 FAQ Schema — add for Google rich results + AI Overviewformat
✗No HowTo Schema — add for step-by-step rich resultsformat
✗No comparison content — add vs. sections for AI recommendationsformat
✗No summary section — add Key Takeaways or TL;DR for AIformat
✗No BreadcrumbList schema — add for better AI contextformat
✗Only one list type — use both <ul> and <ol> for content varietyformat
✗Only 2/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 conclusion — add recommendations or a verdict sectionformat
✗No <time> elements — wrap dates in <time datetime="...">semantic
✗Few data points with units — add specific numbers (e.g., "300+ users")semantic
✗Incomplete Open Graph tags — AI uses these for contexttechnical
✗Only 239 words — AI systems prefer content with 300+ words for comprehensive analysisoverview
✗First 200 words lack topic keywords — AI may skip your content for extractionoverview
✗Missing definition or list format — combine "X is..." with lists for snippetsoverview
✗Only 0 data points — add 5+ statistics for +30-40% AI visibility (Princeton study)authority
✗Author lacks credentials — anonymous content is a GEO penaltyauthority
✗Only 1/6 question types — add What, Why, How headingsoverview
✗No <figure>/<figcaption> — wrap images with descriptive captions for AIformat
✗No authoritative sameAs links — add Wikipedia/Wikidata/LinkedIn URIs to schema for Knowledge Graph alignmentauthority

Passed Checks (24)

✓Content freshness signals detectedoverview
✓Title and H1 are aligned — clear topic focusoverview
✓2-level heading hierarchy — deep content structureoverview
✓Author schema markup foundauthority
✓Brand identity consistent (OG + Schema)authority
✓13 images all with ALT text — AI can understand visualsformat
✓Data visualization elements found (tables/charts)format
✓3 entity types in Schema — AI can classify contentsemantic
✓5/14 semantic HTML5 elements — deep semantic structuresemantic
✓100% title keywords in first 200 words — good prominencesemantic
✓10 contextual links — good cross-referencingsemantic
✓Content categorization found — clear topic classificationsemantic
✓2 sections have subtopics (H3) — deep coveragesemantic
✓Mobile-friendly (viewport set)technical
✓HTTPS secure — trusted by AI systemstechnical
✓Page size: 49 KB — reasonabletechnical
✓Canonical URL set — prevents AI from citing duplicatestechnical
✓Page allows AI indexing (no noindex/nosnippet)technical
✓5 Schema types — rich structured datatechnical
✓Language + OG locale set — clear language signaltechnical
✓3 ARIA landmarks found — good accessibility for AItechnical
✓All image ALT texts are descriptive (>5 chars)format
✓max-image-preview:large — optimal AI rich result displaytechnical
✓Link anchor texts are descriptive — good AI context signalsemantic

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

Scan This Site Again Request Report Removal