ThreadPage
Start writing

All use cases

An SEO change log, with the evidence you return to

Each change to titles, links or pages is a dated note. Four weeks later a reminder brings it back, and the Search Console screenshot goes in a note that references the change.

Start writing

Free in your browser. No account needed to start.

See the thread

At a glance

For
SEO specialists and marketers who change a site and need to know what worked.
You keep
One thread for the site’s SEO changes, with a reminder on each change.
Nothing to set up
A note for each change, and four weeks later the result as a screenshot.
The moment
Four weeks after the title change, Remind me… brings its note back. Add the Search Console screenshot, compare queries and impressions, and record other changes before deciding what to try next.
Plan
Free Free keeps the log in this browser. Sign in to get reminders on this device. Plus adds Sync across your devices. Pro with Sync adds sharing and the optional connections below.

Before

In April traffic to the pricing page fell by a third. Since then you’ve changed titles, merged two guides and moved the blog. Which change did it? The commits say what changed, not why, and Search Console doesn’t know what you did.

Why a thread, not commits and Search Console

  1. What changed, and when

    The page, the old title and the new one, in a note dated the day it went live.

  2. Back when the data is in

    Set Remind me… on the note for four weeks later, when you have a comparable period to review.

  3. The result points to the change

    The screenshot goes in a note that references the change it measures, so the evidence stays connected to the change.

A thread, over time Example

Your workspace starts empty.

Website

SEO changes

Active

  1. Mon 7 Sept

    1. The change, the day it went live. Remind me… set for 5 October.

      You14:00

      PageOld titleNew title
      /pricingPricingPlans and features for your next project

  2. Mon 14 Sept

    1. You11:30

      Merged the two export guides into one; the old address redirects.

  3. Mon 5 Oct

    1. The reminder brought it back; the result references the change.

      You09:30

      Four weeks after the new pricing title: clicks up 18%, average position from 7.2 to 5.9. Check the queries, impressions and other changes before attributing the increase. #review

      SEO changes · 7 Sept

    2. You09:45

      Next: check the query mix and changes on comparable pages before updating more titles.

  4. Mon 12 Oct

    1. With Pro, each site release files itself from GitHub.

      via GitHub16:20

      Site release 2026.10.12

      github.com/acme/website/releases/tag/2026.10.12

      New titles on five pages.

If you like, let it file itself.

None of this is needed to start. It takes a few minutes once, and needs Pro.

Script or API

  • Site releases from GitHub

    Each release you publish for the site becomes a note in the log, with its notes.

    Set it up

    AutomationAdd notes from another appGitHub releases

    1. In Settings → Connections → Automations, choose Connect an automation → Add notes from another app. Name it GitHub, choose SEO changes and GitHub releases.
    2. In the site repository’s Settings → Webhooks, paste the URL and the secret, choose application/json and Releases.

  • Ask what worked

    Write to @GPT or @Claude in the thread. It reads the log and answers with a note, on your own API key.

    Set it up

    AI modelYour OpenAI or Anthropic API keyPro with Sync

    1. In Settings → Connections, open AI models, choose Claude or GPT, paste an API key from Anthropic or OpenAI and choose Connect. AI models need Pro with Sync turned on.
    2. In the thread, write @GPT and your question, then choose Send.

Also

If Claude Code or Codex edits your site, one rule in CLAUDE.md or AGENTS.md can have it add a note to SEO changes for each title it changes, once you connect it with Pro (see Coding agents help).

Limits

  • There’s no Search Console connection: you add the screenshots, and Search finds the numbers you write next to them.
  • A reminder says when, not what: the note it opens says the rest.
  • On Free your notes stay in this browser: export a backup now and then.

Google Search Console, GitHub, GPT, Claude, Claude Code, Codex, OpenAI, and Anthropic are the names of their owners. ThreadPage is independent and not affiliated with or endorsed by them.

Start with one thread.

Start writing

Free in your browser. No account needed to start.

More use cases

  • Every piece of content, from idea to published

    A thread per article or episode, with your own statuses from Idea to Published. On Monday, List filtered to Draft shows what to finish this week.

    Free your own statuses

  • A campaign, from brief to results

    The brief, the creatives, the weekly numbers and every decision in one thread. At the review, the note beside the numbers explains why the budget moved.

    Free nothing to set up
All use cases