Mapping SEO Reality: Pillar One of the Six Pillars

Run an SEO baseline audit as pillar one of the six pillars: shared history, the futures triangle and the futures landscape applied to your site.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

Mapping is the first of the six pillars in Sohail Inayatullah's futures framework. In mapping, "past, present and future are mapped", so that a group becomes clearer on where it has come from and where it is going (Inayatullah, Futures Studies: Theories and Methods). This skill applies that pillar to a website. The result is an SEO current reality audit, the six pillars framework audit that later pillars build on, and it goes further than a technical checklist: it records the site's history, the forces pushing it forward, the weights holding it back, and the futures people in the organization are aiming at.

A standard SEO baseline audit counts things: pages, rankings, traffic, errors, links. Those counts are necessary and this skill includes them. What mapping adds is context. The same traffic decline means one thing after a site migration and another after a competitor published a better guide. The same thin archive means one thing if leadership plans to expand the topic and another if it plans to leave it. Mapping puts the numbers inside a story that the team agrees on.

The Insight & Foresight summary of the paper lists three mapping tools (Insight & Foresight summary). Shared history asks participants to write down the trends and events that led to the present and builds a timeline from them. The futures triangle weighs the pull of images of the future, the pushes of the present and the weights of the past. The futures landscape audits the current state at four levels: the jungle of day-to-day survival, the chess set of strategy, the mountain tops of the big picture, and the star of the vision. This skill uses all three.

The Six Pillars Framework page explains how mapping feeds the other pillars. In short, anticipation needs the map to judge which emerging issues matter, and backcasting needs it as the starting point it works back to.

How It Works

The audit has two halves: the quantitative baseline and the three mapping tools that interpret it.

The quantitative baseline is the familiar part. Inventory the site's indexable pages by topic. Pull query and page data from Search Console, which keeps 16 months of performance data for year-over-year comparison. Crawl the site for technical problems, orphaned pages and duplicate content. Record which competitors appear for the queries you care about and how their coverage compares with yours.

Shared history comes next. Gather people who have worked on the site and build a timeline of events that shaped its search position: launches, migrations, redesigns, content pushes, product changes, algorithm updates the team noticed, and changes in staff. Then lay the traffic and visibility data over the timeline. Inayatullah's version asks what is continuous in the history and what is discontinuous. For a website, the discontinuities often line up with the biggest changes in the numbers.

The futures triangle turns the baseline into forces. In the Journal of Futures Studies interview, Inayatullah calls the triangle the most useful mapping tool and describes its three aspects: a quantitative one (the pushes of the present), a qualitative one (the weight of history) and a visual one (the pull of the preferred future) (Journal of Futures Studies interview). For a site, the pushes are measurable trends in demand, visibility and competition. The weights are what resists change: technical debt, an archive of weak pages, a brand associated with another topic, approval processes that slow publishing. The pulls are the images of the future held by leadership, product and the content team, which often differ from each other.

The futures landscape sorts the findings by level. Jungle items are about survival this month: broken pages, lost rankings, indexing problems. Chess set items are strategic: which topics to compete for and against whom. Mountain top items are the wider context: how search itself is changing and where the market is heading. The star is the organization's vision for its content. A healthy map has findings at every level. A map with only jungle items is a technical audit and will produce a technical plan.

The deliverable is a short written map with the baseline figures, the timeline, the triangle, and the landscape, followed by the few conclusions the team agrees on.

Step-by-Step Guide

Step 1: Set the scope and invite the right people

Decide which part of the site the map covers: the whole domain, a section, or one topic area. List who should contribute: the content and SEO leads, someone who knows the site's technical history, and people from product and sales who hear what customers ask. Agree on the date range for the data. Share the purpose so contributors know this is a shared picture and not a performance review.

Step 2: Build the quantitative baseline

Inventory pages by topic, with each page's main queries, clicks, impressions and position from Search Console. Crawl the site for indexing problems, orphaned pages, duplicate content and broken links. Record the main competitors for your key topics and note where their coverage is deeper or shallower than yours. Keep the baseline in one sheet so later pillars can reuse it.

Step 3: Build the shared history timeline

Ask contributors to list the events and trends that shaped the site's search position. Arrange them on a timeline and overlay the traffic and visibility data. Mark the discontinuities: points where the numbers changed direction. For each, record the team's best explanation and how confident they are in it.

Step 4: Draw the futures triangle

List the pushes of the present from the baseline data: rising or falling demand, competitor moves, changes in how results are presented. List the weights of the past: technical debt, weak archive content, brand associations, slow processes. Collect the pulls: the images of the future that leadership, product and the content team hold. Note where the pulls conflict, because the transforming pillar will need to resolve them.

Step 5: Sort findings with the futures landscape

Place each finding at one of the four levels: jungle, chess set, mountain tops or star. Check that every level has entries. If the star is empty, ask leadership for the vision the content should serve. If the mountain tops are empty, add the wider changes in search and in your market that the team already knows about.

Step 6: Write and agree the current-reality map

Write the map as a short document: the baseline summary, the timeline, the triangle and the landscape. End with a handful of conclusions, such as where the site is strong, where it is weak, and what most constrains change. Review it with contributors and revise until they accept it as accurate. Date it and store it where the next pillars will use it.

Best Practices

• Combine numbers and history. Data without the timeline is easy to misread. The timeline without data turns into anecdote.
• Include people outside the content team. Sales, product and support see what customers ask and what the site misses. Their view often changes the conclusions.
• Name the weights honestly. Technical debt, slow approvals and an off-topic brand are real constraints. Leaving them off the map makes every later plan too optimistic.
• Record conflicting futures. Different pulls among leaders are normal. Writing them down early prevents a roadmap built on one person's assumption.
• Keep the map short. A few pages that everyone reads beat a long audit nobody finishes. Put detail in the appendix sheet.
• Date the map and refresh it. Update it in each quarterly review so later pillars always work from a current picture.

Common Mistakes

• Treating a technical crawl as the whole map: A crawl finds jungle-level problems. Add the timeline, the triangle and the higher landscape levels, or the plan will only fix errors.
• Mapping from memory: The team's sense of which pages matter is often wrong. Check every claim against Search Console and analytics data.
• Skipping competitors: Your visibility depends on what others publish. Include the competitors that appear for your key queries.
• Letting one view dominate: If only the SEO lead contributes, the map reflects one set of assumptions. Invite people who see the site differently.
• Never agreeing the map: A map that contributors dispute will be ignored later. Review and revise it until the group accepts it.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: Six Pillars Framework

Related Skills

• B2B SEO Six Pillars: Adapting the Framework
• Building Topical Authority With Content Clustering
• Semantic Keyword Mapping for Pillar Content
• Designing Content Cluster Architectures
• Six Pillar SEO Strategy: Implementing End to End
• SEO Scenario Planning for Alternative Futures
• Timing Content Interventions for SEO Pillars

Sources

• Futures Studies: Theories and Methods, Sohail Inayatullah
• Six Pillars: Futures Thinking for Transforming, Insight & Foresight summary
• Interview with the UNESCO Chair in Futures Studies, Journal of Futures Studies
• Introducing the new Search Console, Google Search Central Blog

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.