track_gsc_property

Cost: Free (0 credits).

track_gsc_property turns a Search Console property into a tracked project in one call. It works out the site's domain from the property, opens the project for it — or brings it back from your archive — and links the property to it, ready for pull_gsc_data.

What it does

Pass a property as list_gsc_properties prints it — or just the site's host, example.com. SeoGrep re-reads your Google accounts live and only accepts a property one of them actually lists; what you type is never taken as proof it exists. If you already have a project for that site, it is reused rather than duplicated — running this twice with the same property changes nothing. If the same property sits on two of your connected accounts, SeoGrep asks which one to read it through instead of guessing, and you re-run with account_id.

Running it with a different property for a site you already track is not a no-op: it repoints the project at the new property, and the old link is gone. That is a supported call, not an accident, but it is a change of data source rather than a repeat of the last one.

A bare host is resolved — unless it is ambiguous

example.com is the form people type from memory; sc-domain:example.com and https://example.com/ are the forms Search Console prints. A bare host is matched against the properties your accounts really list, ignoring a leading www. on either side, and is accepted when exactly one property names that site.

When more than one does, the tool offers the choice and stops. sc-domain:example.com and https://example.com/ are two different properties with different data and different permissions, so the answer lists the candidates and asks you to re-run with the one you want, spelled as it is printed. Picking one for you would bind the project to a source you did not choose, and a wrong binding only shows up much later, when the data stops making sense.

The same www. blindness applies to the project side: a property for example.com finds a project stored as www.example.com rather than opening a second project beside it. Only the leading www. label is ignored — a subdomain is a different site.

Domain properties and disavow

When the property you bind is a Domain property (sc-domain:example.com), the answer carries one extra note: Google's disavow links tool does not support Domain properties, so a disavow file for that site has to be submitted through a URL-prefix property instead. It is said here because this is where the kind of property is known — disavow_candidates is where you would otherwise find out. A URL-prefix property gets no such note; the limitation does not apply to it.

When it refuses

A property your account cannot query is refused before any project is created — a project that looks tracked but can answer nothing is worse than no project, so the answer names the permission level and what to do about it. A property no connected account lists is refused the same way. And if Google could not be reached at all, you are told the account could not be read, never that the property is missing: an absence we did not observe is not an absence.

The same rule applies when only some of your accounts answer. If the property is listed on an account that answered while another account could not be read, SeoGrep refuses rather than binding: the silent account might list it too, and a passing outage must not decide which Google account a project reads through. Re-run with account_id to settle it yourself, or try again once the other account is readable.

Archived projects

If you archived the project for this domain earlier, this brings back the same project — its id, its crawls and its reports are all still there. Nothing is started from scratch and no second project is created for the same site.

Example

Ask your MCP client in plain language:

Track sc-domain:example.com in SeoGrep.

Or just name the site — > Track example.com in SeoGrep. — and run list_gsc_properties if the answer comes back asking which of several properties you meant.

Input

Returns

The project the property was attached to — its domain and project_id, whether it was created, already tracked or restored from your archive, which Google account it now reads through, and the tools to run next.