Site & Search

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

• Site digest runs mondays · 8am and keeps the Site & search dashboard fresh. Every Monday: the week's clicks, impressions and positions per page, filed and drawn — and a card only when something moved beyond the usual.
• What is captured lands in the Site record dataset, which lives at Data/Site Snapshots in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Changes record dataset, which lives at Data/Site Changes in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Search plan dataset, which lives at Data/Site Plan in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Page checks dataset, which lives at Data/Site Checks in your vault — yours to open, search, and edit like any other file.
• The Site & search dashboard reads from the dataset and shows, at a glance: search clicks, month by month · pages by search clicks · search clicks on the record · changes you have noted · queries that moved · last week against the week before · the work, by kind · most shown, least clicked · the last twelve weeks · just past the top ten · the last 28 days · your search plan · on google · this week · check a page by hand · the record, week by week · how this board works.

The wiring, in one breath: SEO capture writes to Changes record · Site digest writes to Site record · Site record shown by Site & search · Changes record shown by Site & search · Site & search kept fresh by Site digest · Site digest run by Heather · SEO capture given to Heather · Site review given to Heather · Search planner keeps Search plan · SEO capture updates Search plan · Page check writes to Page checks · Site digest updates Page checks · Search plan shown by Site & search · Page checks shown by Site & search · Search planner given to Heather · Page check given to Heather.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

• Let the Monday pull read; your job is the glance. Open Site & search after it runs and read Search clicks month by month against Pages by search clicks — the line says whether the site is earning more overall, the bar says which pages are carrying it, and one without the other is how a single page’s good month gets mistaken for a trend.
• Say what you changed, in passing, the day you do it: “I rewrote the pricing page title this morning”, “merged those two thin docs pages”. SEO capture puts it on the timeline with its date, and that timeline is what makes next month’s figures readable. A change you did not record is a movement you will have no way to place.
• Ask Heather before you conclude anything: “how is the pricing page doing?” Site review reads that page’s weeks back — clicks, impressions, the range its position has been sitting in — and says which site and which dates it used, so the answer is checkable rather than just quotable. It will also tell you when a swing is inside that page’s ordinary week-to-week range, which is usually the most useful thing anyone can say about a bad week.
• Read impressions beside clicks, never alone. A page with impressions and few clicks is being shown and not chosen; a page with neither is not being shown at all. Those are different problems and the board keeps both numbers on the same row so you can tell them apart.
• Treat the timeline as an order of events, not a verdict. Heather will show you that you rewrote a page on the 14th and that its clicks moved in the week after, and will not state as fact that the first caused the second — because nothing in these records can show that. Ask why and it names the likely causes and how sure it is; deciding what it means is the part that is yours.
• Tell Heather what a normal week looks like for you at the calibration, and the Monday card stays worth reading. Without a threshold it flags whatever moved furthest; with one it stays quiet through the ordinary wobble and speaks up when something is genuinely out of range.
• When you are deciding what to work on, read Most shown, least clicked beside Just past the top ten. The first is your own record’s last twelve weeks: the pages Google shows most and people choose least for the times they are shown. The second is the searches where the site sits from 11 to 20 on average. Both are figures and neither is a forecast: Heather puts no number on what a change would bring; ask where to start and it says, and which to work on is yours.
• Keep the plan with Heather rather than in a spreadsheet: “put a page comparing our plans on the list, for pricing comparison, by the end of November”. Search planner writes it in your words on the Search plan, and Your search plan on the board is where you tick it off. Tell Heather when you finish something and she offers to put it on the changes timeline, so next month’s figures have something to be read beside.
• Before you rewrite a page, ask Heather to check it: “check the pricing page”. Page check reads it, asks Search Console what Google makes of it, and sets each finding beside what Google’s own guide says, with the guide named. What it cannot see from here (the page on a phone, the description search results show, how fast it loads) goes to Check a page by hand on the board, one thing at a time. Name another site’s page and it is laid beside yours on the same list, with Heather’s view if you ask.
• Ask for keyword research and you get the searches the site already appears for around your subject, with how often it was shown and where it sat, and how published pages word the subject, each one named. You will not get a search volume: nothing here can measure one, and Heather says so rather than inventing a figure.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

• Which Search Console site and which analytics property are yours — said once, remembered, so no later pull has to choose.
• Which handful of pages actually matter to you. The record holds whatever earned clicks; naming the ones you care about is what decides which movements are worth a card, and which pages On Google checks each Monday.
• What you want the site to be found for, which is what the Search planner plans around; say so again whenever it changes.
• How far a figure has to move before you want telling. Set it in your own words and Heather stays quiet through the ordinary week-to-week wobble.
• Sections of the site to leave out of the record altogether — a staging path, an internal area, anything you would rather not keep figures on.
• When the pull runs, or pausing it and keeping the changes timeline by hand — anything you mention is captured either way.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

1. Adding the Kit offers the first pull right away: once Search Console and your analytics property are connected on the Connectors screen, start it with one tap, and watch Heather read six months back — which pages earned clicks each week, how often they were shown, roughly where they sat, and how many times they were read — and build the weekly record from it. The board has a real trend on it before you have typed anything. Prefer not to connect? Tell Heather what you have been changing on the site instead, and the timeline starts by hand. Either way, Heather starts from what 1Presence already knows, your memory and any changelog or audit in your vault, and asks only for the gaps.
2. When that first pull finishes, Heather leaves a short note in your 1Presence inbox saying what it filed — how many weekly rows, across how many pages — and invites a few minutes together on the things only you know: which property and site are the right ones, which handful of pages you actually care about, how far a number has to move before you would want telling, and the fixes you have already made, so the timeline reaches back before the pull did. In passing, Heather also asks once what you most want the site to be found for, which is what the Search planner plans around, and whether anything is on your search plan.
3. What is still missing waits on the Kit page with a way back to Heather, and Heather offers it once the next time you talk. Tell her a part does not apply to you, or that you have finished setting up, and she stops asking.
4. From then on the pull runs every Monday morning. It files the week just gone and re-files the one before it — Search Console’s figures lag two to three days, so a week is still settling when it is first written, and the record corrects it rather than counting it twice. Then it redraws the board, works out the pages shown most and clicked least and the searches just past the top ten, checks that Google still has the pages you watch, and raises a card only when something moved beyond that page’s ordinary range, or a page you watch has dropped out of Google.
5. Two things this Kit deliberately does not do, and says so on the board. It has no coverage panel: Search Console’s own interface has an index-coverage report and its API does not, so instead of a list of the site’s problems, On Google checks the pages you watch each Monday, and Heather will inspect any other page you name and tell you exactly what Google says about that one. And it never states as fact that a change you made caused a number to move — it puts both on one timeline first, and names the likely causes if you ask.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits