SEO Shift Log

Help & Documentation

Learn how to connect Search Console, record SEO work, read equal comparison periods, and share clear client reports.

Your first complete session

  1. Sign in with the secure link sent to your email.

  2. Connect a Google account with Search Console access.

  3. Choose a verified property to add to the workspace.

  4. Wait while finalized page-level history is stored.

  5. Log a real page change and follow its comparison windows.

Getting started

From an email sign-in link to the first stored Search performance history.

Sign in without a password

Enter your work email on the sign-in page. SEO Shift Log sends a secure, single-use link to that address. Open the newest link on the same device where you want to use the app.

If the link has expired or was already used, return to the sign-in page and request a fresh one. SEO Shift Log does not store an account password.

Choose the first property

After connecting Google, select a Search Console property you are authorized to manage. Evaluation access includes one property. A subscription is needed before adding more.

Initial history is collected in the background. You may leave the page and return later without restarting the work.

Search Console access

What SEO Shift Log reads, stores, and never changes.

SEO Shift Log requests Google's webmasters.readonlypermission. It can list accessible properties and read page-level clicks, impressions, click-through rate, and average position. It cannot edit your website or Search Console settings.

Select the Google account that already has access to the intended property. If a property is missing, confirm that it appears in Search Console for that same Google account.

Revoke or reconnect access

You can revoke access from your Google Account at any time. Revocation stops future synchronization but does not automatically delete history already stored in SEO Shift Log. Use the reconnect prompt in the app when you want synchronization to resume.

Open Google's third-party connections

Logging changes

Create a dated record that another person can understand later.

From a Site Dashboard or Change Log, select Log a Change. Record the page URL, change date, type of work, short title, and what changed. Use the canonical page URL reported by Search Console when possible.

The optional expected outcome captures what you thought might happen before later data arrives. It is a contemporaneous note, not a promise or attribution claim.

Short titleReworked service page title and H1
What changed

Aligned the title and H1 with the primary furnace repair service.

Expected outcome

More relevant impressions for local furnace repair searches.

Reading comparisons

Equal periods before and after a dated change.

Each change supports 7-, 14-, 28-, and 90-day windows. For a window of N days, the before period ends the day before the change and the after period begins the following day. The change date itself is excluded because it may contain only partial exposure.

Clicks
Visits from Google Search results.
Impressions
Times a result was shown in Google Search.
CTR
Clicks divided by impressions for the period.
Average position
An impression-weighted average; a lower number is better.
“Not available” does not mean zero.

It means the required Search Console figures have not been stored for that side of the comparison. Coverage is shown independently for the before and after periods.

A difference describes performance following a change. It does not establish that the change caused the difference. Seasonality, algorithm updates, and other work may affect the same figures.

Client reports

Publish a read-only snapshot without exposing the workspace.

  1. Create a draft for one property and reporting period.
  2. Add a title, introduction, selected changes, and closing notes.
  3. Review every page URL, note, and comparison before publishing.
  4. Choose whether the public link expires after 7, 30, or 90 days, or never.
  5. Copy the link when it is shown and send it only to the intended recipient.

Publishing freezes the report exactly as it appears at that moment. Later Search Console synchronization does not rewrite the published evidence. Anyone with the link may be able to view it until it expires or is revoked.

Revoke a link to stop access. Rotate it when the report should remain published but the previous URL should no longer work.

Plans and capacity

Site limits control expansion without deleting recorded work.

Open Billing & Sites to see the active plan, billing status, connected-property count, and remaining capacity. Checkout and payment-method management are hosted by Stripe. SEO Shift Log does not store complete card numbers.

If a payment problem or plan change reduces available capacity, existing sites and stored evidence remain readable. Additional properties cannot be added until the subscription and capacity allow it.

Troubleshooting

Start with the symptom that matches what you see.

The sign-in email did not arrive

Check the spam folder and confirm the address was entered correctly. Wait briefly before requesting another link. Use only the newest link because each one is single-use and expires.

A Search Console property is missing

Confirm you selected the Google account that can see the property in Search Console. Verify the property there or reconnect using another authorized Google account.

History is still collecting

Initial history and recent finalized dates are synchronized in the background. The dashboard shows exactly how many days are stored. Missing days remain unavailable rather than being displayed as zero.

A comparison is not ready

Check the before and after coverage separately. The complete comparison appears only after all required dates for the selected window have been stored.

A published report link no longer opens

The link may have expired, been revoked, or been replaced by a rotated link. Open the report inside the workspace and publish or rotate access as appropriate.

A billing change is not visible yet

Stripe confirms subscription changes through a signed webhook. Refresh Billing & Sites after a short wait. If the status still disagrees with Stripe, contact SEO Shift Log and include the approximate checkout time.

What to include in a support request

Send the approximate time and time zone, the page you were on, what you selected, what happened, and any visible support reference. A screenshot is helpful. Never send a password, magic-link URL, Google authorization code, Stripe key, or full card number.