AI Visibility Audit
NO EN
Auditing … this usually takes 5–20 seconds.
Download JSON Run again
Audit of
https://pk-eiendom.no/ansatt/christian-natadal/
Audited 13.10.2026 08:55 · 2.1 s
2 errors 2 warnings 44 OK 2 info
89
out of 100
+0.0
since 13.10.2026
AI bot access93
Content & structure67
Technical SEO97
Structured data100
Metadata86
Performance100

Priority actions

  1. Error Indexing directives (meta robots / X-Robots-Tag)
    noindex/none makes search engines and AI search drop the page entirely, even if robots.txt allows access. Remove the directive if the page should be visible (check SEO plugins like Yoast/Rank Math and "Search engine visibility" under Settings → Reading in WordPress).
  2. Error Content without JavaScript
    Almost no content in the raw HTML. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) do not run JavaScript and therefore see an almost empty page. Use server-side rendering (SSR) or pre-rendering, or make sure the theme/page builder outputs the text in the HTML.
  3. Warning Canonical
    Add <link rel="canonical" href="…"> pointing to the preferred address. It stops duplicates (with parameters, www/non-www) from competing.
  4. Warning Image alt text
    6 images from the media library have empty alt (alt=""). That means "purely decorative", but photos of staff, properties and products are content and should have a short description, e.g. the person's name. Add alt text in the media library, or check that the theme actually uses it.

AI bots

The bots for AI search and citations matter most – if they are blocked, the site does not appear in answers. Blocking training bots is often deliberate and does not lower the score.

Bot Purpose robots.txt Server Status
OAI-SearchBot
OpenAI (ChatGPT search)
AI search & citations allowed responds normally (HTTP 200) OK
Claude-SearchBot
Anthropic (Claude)
AI search & citations allowed responds normally (HTTP 200) OK
PerplexityBot
Perplexity
AI search & citations allowed responds normally (HTTP 200) OK
Googlebot
Google (Search, AI Overviews, Gemini)
AI search & citations allowed not tested OK
Bingbot
Microsoft (Bing + Copilot)
AI search & citations allowed not tested OK
Applebot
Apple (Siri/Spotlight)
AI search & citations allowed not tested OK
ChatGPT-User
OpenAI (ChatGPT)
Fetch on behalf of user allowed responds normally (HTTP 200) OK
Claude-User
Anthropic (Claude)
Fetch on behalf of user allowed responds normally (HTTP 200) OK
Perplexity-User
Perplexity
Fetch on behalf of user allowed responds normally (HTTP 200) OK
GPTBot
OpenAI
Model training allowed responds normally (HTTP 200) OK
ClaudeBot
Anthropic
Model training allowed responds normally (HTTP 200) OK
Google-Extended
Google (Gemini training)
Model training allowed not tested OK
Applebot-Extended
Apple (Apple Intelligence training)
Model training allowed not tested OK
CCBot
Common Crawl
Model training allowed responds normally (HTTP 200) OK
Meta-ExternalAgent
Meta
Model training allowed responds normally (HTTP 200) OK
Amazonbot
Amazon
Model training allowed responds normally (HTTP 200) OK
Bytespider
ByteDance
Model training allowed responds normally (HTTP 200) OK

The server test fetches the page with the bot's identity from this server. Some firewalls block fake bots by IP address while letting genuine bot traffic through – confirm any blocks in the firewall log. Googlebot, Bingbot and Applebot are only checked against robots.txt.

All checks

AI bot access · 93/100 1 3

Whether AI services and search engines can access the page at all: robots.txt, firewall/CDN blocking, noindex directives and llms.txt. If the AI search bots are blocked here, nothing else helps.

Error Indexing directives (meta robots / X-Robots-Tag)
The page asks not to be indexed: <meta name="robots">: noindex.
noindex/none makes search engines and AI search drop the page entirely, even if robots.txt allows access. Remove the directive if the page should be visible (check SEO plugins like Yoast/Rank Math and "Search engine visibility" under Settings → Reading in WordPress).
OK robots.txt
robots.txt exists and can be read.
OK robots.txt: all bots (*)
The rule for all bots (User-agent: *) allows this page.
OK llms.txt
llms.txt found: title "PK Eiendom", 3 sections, 62 links.
Content & structure · 67/100 1 4 1

Whether the content can be read and understood without JavaScript: amount of text, heading structure, language and whether it is clear when the page was last updated.

Error Content without JavaScript
Main content: 2 words (whole page: 299 words, text share 2.5 %).
Almost no content in the raw HTML. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) do not run JavaScript and therefore see an almost empty page. Use server-side rendering (SSR) or pre-rendering, or make sure the theme/page builder outputs the text in the HTML.
OK H1 heading
One H1: "Christian Natadal"
OK Heading hierarchy
1 headings with no skipped levels.
OK Language (lang attribute)
Language: nb-NO
OK Last updated
Last updated 2026-07-23 (JSON-LD dateModified, 81 days ago).
Info hreflang
No hreflang (fine for single-language sites).
Technical SEO · 97/100 1 9 1

The technical foundation for search and AI: HTTPS and www variants, mobile view, images, internal links and whether the page is in the sitemap.

Warning Image alt text
10 images: 0 without alt attribute, 7 with empty alt (decorative). 6 of the images with empty alt look like content images.
6 images from the media library have empty alt (alt=""). That means "purely decorative", but photos of staff, properties and products are content and should have a short description, e.g. the person's name. Add alt text in the media library, or check that the theme actually uses it.
Empty alt – treated as decorative (1). Check that these really are decorative.
OK Sitemap
Sitemap index found with 2 sub-sitemaps (https://pk-eiendom.no/sitemap_index.xml). 2 of 2 entries have lastmod.
OK Sitemap in robots.txt
Declared in robots.txt: https://pk-eiendom.no/sitemap_index.xml
OK HTTPS
The page uses HTTPS. http:// redirects to https://. HSTS: max-age=15768000.
OK www / non-www
www.pk-eiendom.no redirects to pk-eiendom.no.
OK Mixed content
No resources are loaded over insecure http.
OK Mobile view (viewport)
viewport="width=device-width,initial-scale=1.0"
OK Image dimensions in HTML
0 of 10 images lack width/height.
OK Internal links
24 internal and 8 external links.
OK Link text
All links have descriptive text.
Info Page in sitemap
The page is not in the sitemap, which is correct since it has noindex.
Structured data · 100/100 4

Structured data (schema.org/JSON-LD) that tells machines who is behind the site and what the page is about – and whether products, events, articles etc. meet Google's requirements.

OK JSON-LD
16 objects: WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization, PostalAddress, ContactPoint
OK Key schema types
Found: WebPage, BreadcrumbList, WebSite, Organization.
OK Organisation / business
Organization has all recommended fields.
OK Schema: breadcrumbs
1 × BreadcrumbList. All required and recommended fields are present.
Metadata · 86/100 1 3

Title, meta description, canonical and Open Graph – what search engines and AI show and use when summarising or linking to the page.

Warning Canonical
Missing canonical link.
Add <link rel="canonical" href="…"> pointing to the preferred address. It stops duplicates (with parameters, www/non-www) from competing.
OK Page title (<title>)
"Christian Natadal - PK Eiendom" (30 characters)
OK Meta description
154 characters: "Siden 1986 har PK Eiendom utviklet og forvaltet eiendommer som skaper vekst, arbeidsplasser og levende lokalmiljøer. Me…"
OK Open Graph
og:title, og:description and og:image present.
Performance · 100/100 4

How quickly and efficiently the server delivers the page. Slow or heavy pages make crawlers fetch fewer pages and may make them give up.

OK Response time
The server responded in 22 ms.
OK HTML size
HTML: 82.8 KB
OK Compression
Compressed with gzip.
OK Number of resources
23 resources: 9 JS, 5 CSS and 9 images (0 of the images load only on scroll). 23 are fetched on first view.

The score is a weighted average of the categories (AI access 30 %, content 20 %, technical SEO 15 %, structured data 15 %, metadata 10 %, performance 10 %). Critical checks count more than minor ones, and "Info" does not count.