Innholdsaudit: vurder og forbedre eksisterende sider

Hva en innholdsaudit er og hvorfor det er viktig

En innholdsaudit er en systematisk gjennomgang av sidene på et nettsted for å fastslå hver sides strategiske rolle, kvalitet og ytelse. Auditen går utover å liste opp URL-er: den spør om en side bør beholdes som den er, forbedres, slås sammen med en annen side, omdirigeres eller fjernes. For nettsteder organisert rundt pillar-and-cluster-topic-modeller, forhindrer jevnlige auditer tematisk overlapp og holder innholdsarkitekturen fokusert.

Definer klare mål og omfang før du starter

Før du samler data, bestem hva suksess ser ut som for denne auditen. Vanlige mål inkluderer å konsolidere redundante sider, forbedre tematisk dybde for målrettede klynger, hente tilbake trafikk til historisk høytytende innlegg eller forbedre konverteringsflyten. Avgrens auditen etter nettstedseksjon, innholdstype (blogginnlegg, produktsider, hjelpartikler) eller etter datoperiode hvis du vil fokusere på eldre innhold.

Step-by-step audit workflow

1) Create an inventory

Samle en komplett liste over sider innenfor det omfanget du har valgt. Kilder å kombinere:

• Sitemap-filer og alle programmatisk genererte sitemaps
• Site crawl fra en crawler (eksporter hele URL-listen)
• Sider med målbar trafikk fra analytics-plattformen din
• High-value landing pages identifisert av forretningsansvarlige eller produktteam

2) Add performance and discovery signals

Berik inventaret ditt med observerbare metrikker og signaler slik at du kan ta informerte beslutninger. Typiske dimensjoner:

• Organic visibility: queries, impressions, clicks, and CTR from Google Search Console Performance report (for properties you own)
• Indexation status: use URL Inspection in Google Search Console to see if a URL is indexed and whether Google is using the canonical you expect
• Engagement and conversion metrics from your analytics (sessions, bounce/engagement, goal completions)
• Internal linking: which pages point to this URL and anchor text used
• Content attributes: publish date, word count, core topic, content type, author, presence of structured data
• Technical signals: HTTP status, canonical tag, hreflang where applicable, server response headers

3) Classify outcomes: keep, improve, merge, redirect, remove

Use a short decision framework for each URL. Consider intent-match, topical uniqueness, current visibility, conversions, and internal-link support. Typical outcome definitions:

1. Keep — page is on-topic, matches clear user intent, and performs well or has strategic value.
2. Improve — the page is relevant but thin, outdated, or missing structured answers; update content, add depth, and improve internal linking.
3. Merge — two or more pages compete for the same intent. Combine signals and use a single canonical URL with a 301 redirect from the merged pages.
4. Redirect — if a page has little unique value but useful backlinks or internal links, preserve link equity by redirecting to the best substitute.
5. Remove (410 or delete) — pages with no value, harmful duplicate content, or legal/privacy concerns should be removed. Confirm consequences before deleting.

Practical checks and verification

Indexation and canonical verification

For pages you own, use Google Search Console URL Inspection to confirm indexation, canonical chosen by Google, and any indexing issues. Remember: the site: operator can indicate whether Google shows a page publicly, but it is not a definitive indexation signal. URL Inspection is authoritative for properties you control.

Crawl and render checks (server and device parity)

Because Google uses the mobile version as its primary basis for crawling and indexing and crawls with Googlebot Smartphone by default, confirm that the mobile HTML provides the same critical content and structured data as desktop (parity). Use these checks:

• Fetch the page headers: curl -I https://example.com/page to see HTTP status and header hints.
• Fetch the full HTML as a specific user-agent: curl -A "Mozilla/5.0 (iPhone)" https://example.com/page to compare the mobile and desktop responses.
• Use Chrome DevTools to view the rendered DOM and network waterfall; check that key content and schema appear after client-side rendering.

Structured data and rich results

Validate structured data with the Rich Results Test and Schema Markup Validator. Because AI Overviews and enhanced SERP features often rely on clearly marked facts and answerable snippets, ensure your FAQ/HowTo/Recipe markup is accurate and up to date.

Quality checklist: evaluate each page

Use a repeatable checklist when scoring pages. Score items qualitatively so decisions are defensible with stakeholders.

• Topical relevance: does the content answer the target query and fit the pillar-cluster architecture?
• Search intent alignment: is the page informational, commercial, navigational, or transactional and does it fulfil that intent?
• Content depth and originality: is the content unique and does it provide depth beyond other pages on your site and competitors?
• Freshness: are facts, statistics, and product info current?
• Technical correctness: correct canonical, hreflang where applicable, valid status code, fast server response.
• Visibility and accessibility: indexation state, noindex tags, robots.txt blocks, or X-Robots-Tag headers that may prevent indexing.

Actionable improvements and implementation notes

Improve: practical editing steps

When you decide to improve a page, prioritize these concrete edits: clarify the primary keyword/intent, add a succinct lead that answers the core question, add structured headings and an FAQ for quick answers, refresh facts and dates, include internal links from high-authority topical pages, and add or fix structured data where relevant.

Merge and redirect: preserving equity

If merging pages, consolidate the best content into a single canonical URL, implement 301 redirects from removed pages, and update internal links to point to the final URL. Confirm redirects return the expected HTTP status using curl -I and re-run a crawl to ensure no redirect chains remain.

Remove: safety checks before deletion

Before deleting, check for external backlinks, internal links, and legal or archival needs. If backlinks exist, consider a redirect to avoid losing referral traffic. Use your backlink tool of choice to identify referring pages, then decide whether to preserve link equity or request link updates from webmasters.

Link and sponsorship considerations

During an audit you may find pages that contain paid or sponsored links. Follow Google’s guidance: label paid or compensated links with rel="sponsored" and use rel="ugc" for user-generated content. rel="nofollow" remains a valid option for links you don’t want used as a ranking hint. Remember that rel="nofollow" is treated as a hint by Google, not an absolute instruction.

Examples of link attributes in HTML: standard link sponsored link UGC link

Tools and verification checklist

Primary tools to verify technical and content signals (use the ones you have access to):

• Google Search Console: URL Inspection and Performance report for indexation and query-level visibility
• Chrome DevTools: rendered DOM, Lighthouse audits, and network waterfall
• Rich Results Test and Schema Markup Validator for structured data
• Server tools and curl for header and response checks (curl -I for headers; curl -A to fetch HTML as a given user-agent)

Exportable crawlers or site crawls help find duplicate titles, meta descriptions, and orphan pages. Combine crawl data with analytics and GSC exports to make defensible decisions.

Common mistakes and how to avoid them

• Treating the audit as a one-time project. Make audits regular and incremental.
• Relying solely on raw traffic without considering intent or conversion value — some low-traffic pages are high-value for conversions.
• Merging pages without preserving backlinks or updating internal links, which can create lost referral paths or orphaned content.
• Assuming a page is indexed because it previously was — verify current indexation with URL Inspection.

Report structure and stakeholder communication

Deliver a prioritized action list rather than a raw spreadsheet. Group actions by owner and effort (quick wins vs larger projects), and include a roll-up that shows how recommended actions support business goals (traffic recovery, conversion uplift, topical consolidation).

If you want deeper technical checks after the audit, Read the Technical SEO Guide

FAQ