TSEPCONTROL FREE BETA
Menu

Where would you like to go?

Navigation only · no analysis is started

THE CONTROL GUIDE

Understand.
Then choose.

44 controls

Your site has
more to reveal.

Choose your perspective.
Follow the evidence.

What do you want to check?

1. Choose your controls. 2. Continue to enter your URL. These choices will appear in your results.

Your selection · 0 / 44

Selection prepares your scope.

One public page, with your chosen controls. Some will need additional information.

What will be read

This page and a few public sources from the same site. No sign-in to your site. Use a URL without private data. If field measurements are enabled, the URL will also be sent to Google CrUX. Privacy

Check a control to include it in your scope. Open its details to see the evidence to gather.

Access and indexing 0 / 9 in scope
2 rules
Control summary · TS01

What this control is for

“200 OK” can hide the wrong page. TS01 checks the HTTP response and expected content separately for a public reference URL.

Evidence to gather

Confirm the intended public reference use, destination and distinctive text identifying the right page. A wrong response never automatically becomes your reference.

Limits to keep in mind

One URL, the response received at test time and the declared expectation. This result does not cover the whole site, JavaScript rendering or actual indexing.

Read the full guide Check a URL with TS01
2 rules · Guided collection
Control summary · TS02

What this control is for

A working redirect can still take a detour. TS02 compares the actual route with the confirmed plan: destination, number of redirects, permitted status codes and absence of a loop.

Evidence to gather

Confirm the expected destination and permitted route before collection. By default: one permanent 301 or 308 redirect, then 200. Also check permitted domains and collection limits.

Limits to keep in mind

The tested address and its route, at test time, from the TSEP client. This does not automatically cover every variant, the whole site, destination-content relevance or an actual Googlebot visit.

Read the full guide Check a redirect with TS02
1 rule
Control summary · TS03

What this control is for

Put the responses of an existing page, a removed page and a nonexistent address side by side. This helps document an unexpected HTTP status before a correction.

Evidence to gather

Two or three addresses on the same site, with their actual situation. The removed page is optional if you have no example. A removal with a replacement belongs in the TS02 workflow.

Limits to keep in mind

Real URL observations are available. A real-world TSEP verdict is not yet available: the current TS03-A01 rule only qualifies fictional .invalid matrices. This workflow does not classify Google soft 404s or check the entire site.

Read the full guide Read responses with TS03
2 rules
Control summary · TS04

What this control is for

Find a useful page blocked by robots.txt, an address allowed by mistake or an inaccessible required resource.

Evidence to gather

A page that should be crawlable. Optionally: two required resources and two addresses to disallow on the same origin. You confirm this scope before collection.

Limits to keep in mind

Googlebot rules interpreted on the response received by TSEP, and declared resources. No actual Googlebot visit, exhaustive site coverage or indexing established. Obstacle review is supplied by you, never invented by the app.

Read the full guide Check robots.txt with TS04
1 rule
Control summary · TS05

What this control is for

Avoid relying on robots.txt to remove a page from Google or protect private content. This check examines whether your declared methods match your goal.

Evidence to gather

A URL, visibility and access goals, then your planned methods. You can answer “I do not know”. You confirm the recap before the check.

Limits to keep in mind

Your declared model only. No site visit, Google status check or protection test. A consistent plan is not proof that the page has disappeared from search results or that its content is private.

Read the full guide Check my plan with TS05
1 rule
Control summary · TS06

What this control is for

Prepare a useful access check for your technical team.

Evidence to gather

A private URL, allowed users, content to protect and expected denial.

Limits to keep in mind

This workflow prepares a test: no anonymous request is sent and no real access is evidenced. Robots.txt or noindex do not protect private content.

Read the full guide Prepare my access test
3 rules
Control summary · TS07

What this control is for

Spot directives that contradict your goal for Google.

Evidence to gather

A URL and a goal: allow indexing or exclude the page.

Limits to keep in mind

The reading covers one URL and the received HTTP response. It proves neither the response received by Googlebot, nor content after JavaScript, nor actual indexing. Without access or rendering evidence, those points remain unverified.

Read the full guide Read my page’s directives
3 rules
Control summary · TS08

What this control is for

Understand Google-reported status and decide what to do.

Evidence to gather

An authorized Search Console account, one URL and a prior goal.

Limits to keep in mind

Inspection shows what Google reports for this URL; it is not a live test. The documentation result validates neither the whole page nor the whole site.

See what Google knows about your URL using your Search Console data.

Connect Google — new tab Search Console · Read-only · New tab. The inspection creates a dossier separate from this analysis.
Read the full guide Open Search Console
1 rule
Control summary · TS09

What this control is for

Check that an intentional exclusion is explained and its implementation can be observed on one representative page.

Evidence to gather

A representative URL, its page family, the planned method, then your register: rationale, owner and review date. Confirm the scope before the page and its robots.txt are read without login.

Limits to keep in mind

One representative page at capture time, and the supplied register. This proves neither the whole family, nor actual exclusion from Google, nor JavaScript rendering. Disallow prevents crawling; it does not by itself guarantee removal from the index. Your review of the scope and rationale remains personal. The application does not invent it: if missing, that point remains incomplete. Historical dossiers retain the method of their version.

Read the full guide Check my register
URLs and canonicals 0 / 7 in scope
4 rules
Control summary · TS10

What this control is for

Each canonical page publishes an absolute, stable and consistent URL.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

rel=canonical is a strong signal, not a guaranteed directive.

Read the full guide
2 rules
Control summary · TS11

What this control is for

Genuine duplicate variants converge without hiding distinct pages.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Computed similarity does not replace an editorial decision.

Read the full guide
3 rules
Control summary · TS12

What this control is for

Google’s selected canonical is compared with the declared canonical.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Missing required rendering or absent Google canonical: inconclusive. Literal comparison without inferred URL equivalence, live state, causality, TS10 or indexing.

Read the full guide
2 rules
Control summary · TS19

What this control is for

Parameters, filters and calendars do not create an infinite URL space.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

The actual crawled volume requires logs or Search Console.

Read the full guide
2 rules
Control summary · TS20

What this control is for

The URL structure is readable, stable and correctly encoded.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

A readable URL is not sufficient evidence of SEO performance.

Read the full guide
2 rules
Control summary · TS21

What this control is for

Discovered but unindexed URLs are investigated by family.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

A Search Console label describes a state, not always its cause.

Read the full guide
2 rules
Control summary · TS38

What this control is for

Host, case and trailing-slash variants converge on one rule.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Case can be significant depending on the server and application; the rule must be tested, not assumed.

Read the full guide
Sitemaps and links 0 / 6 in scope
2 rules
Control summary · TS13

What this control is for

The sitemap contains only useful absolute canonical URLs.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Declared supplied file/page population; bounded HTML sources and unauthenticated supplied reviews. No inferred real audit, site completeness, whole TS15 result, Google-selected canonical, indexing or ranking.

Read the full guide
1 rule
Control summary · TS14

What this control is for

lastmod reflects a significant change to the page.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Matching date and supplied review do not prove an actual change or its significance. UTC-day or zoned-instant precision; no complete CMS history, ideal freshness or engine processing inferred.

Read the full guide
3 rules
Control summary · TS15

What this control is for

Sitemap size and segmentation limits are respected.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Supplied files only, no observed server or site completeness. No full XSD, lastmod/changefreq/priority values, URL host/path/length, canonical or indexing validation.

Read the full guide
1 rule
Control summary · TS16

What this control is for

Every important page receives at least one crawlable internal link.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Population and importance are supplied, not authenticated. No site completeness, observed acquisition or interaction, editorial value, Google visit, indexing or ranking. Bounded absence does not establish a site-wide orphan. Expected source content and soft404s are not assessed.

Read the full guide
2 rules
Control summary · TS17

What this control is for

Essential links use an a element with a resolvable href.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

C only within the declared strategy. No established visibility, interaction, editorial importance, authenticity, Google visit, indexing or ranking. Source presence is not a universal Google requirement.

Read the full guide
3 rules
Control summary · TS18

What this control is for

Depth and orphan pages are measured within an explicit scope.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Declared graph only: no completeness, site-wide orphan, universal SEO depth, authenticated acquisition/reviews, observed interaction, indexing or ranking. HTTP200 does not verify expected content or soft404s. The reader does not adjudicate supplied rationale.

Read the full guide
Content and rendering 0 / 7 in scope
2 rules
Control summary · TS25

What this control is for

Critical content exists in source HTML or becomes observable after rendering.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Declared scope only, static hypotheses without execution; unauthenticated reviews and attribution. No inferred Google rendering, CSS visibility, truth, structured validity, indexing or global conformity.

Read the full guide
2 rules
Control summary · TS26

What this control is for

Resources required for rendering are neither blocked nor failing.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

An error-free console does not prove indexing.

Read the full guide
2 rules
Control summary · TS27

What this control is for

SPA states and routes produce shareable URLs and consistent server responses.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Choosing SSR, CSR or SSG is not in itself an SEO guarantee.

Read the full guide
2 rules
Control summary · TS28

What this control is for

The document exposes an understandable HTML structure independently of appearance.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Syntax validity alone proves neither quality nor relevance.

Read the full guide
2 rules
Control summary · TS29

What this control is for

Essential content remains available when scripts or styles fail.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Acceptable degradation depends on the component’s function.

Read the full guide
2 rules
Control summary · TS30

What this control is for

Essential metadata is unique, visible and consistent with the page.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Google may rewrite the title link or snippet in search results.

Read the full guide
3 rules
Control summary · TS44

What this control is for

Critical content and evidence remain accessible without undocumented JavaScript execution.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.

Read the full guide
International 0 / 4 in scope
2 rules
Control summary · TS22

What this control is for

Each hreflang variant points to an indexable canonical URL.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

hreflang helps targeting; it does not replace genuinely localized content.

Read the full guide
1 rule
Control summary · TS23

What this control is for

hreflang annotations are reciprocal and include the current page.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Supplied cluster and primary mode declarations: no capture authenticity, site completeness, TS22 language validity, indexability/canonical, TS24 x-default suitability, translation, executed JavaScript or Google processing. Relevant supplied sitemap/DOM channels remain outside this profile.

Read the full guide
1 rule
Control summary · TS24

What this control is for

x-default represents a neutral destination or an explicit default variant.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Supplied scope, no representative audience or authenticated semantic role; HTTP200 does not detect error templates/soft404s. No translation, Google visit, indexing, completeness or global conformity.

Read the full guide
2 rules
Control summary · TS40

What this control is for

The hreflang methods in use are complete and consistent.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Combining HTML, headers and sitemaps offers no search benefit and increases divergence risk.

Read the full guide
Structured data 0 / 3 in scope
3 rules
Control summary · TS31

What this control is for

JSON-LD describes entities that are visible and appropriate to the content.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Valid markup guarantees neither a rich result nor higher rankings.

Read the full guide
3 rules
Control summary · TS32

What this control is for

Stable @id values connect the same entities without creating duplicates.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Schema.org defines a vocabulary; interpretation depends on the consumer.

Read the full guide
3 rules
Control summary · TS33

What this control is for

Errors, warnings and unsupported uses are distinguished.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Vocabulary names and roles only; no inferred complete semantic validity, cross-snapshot correspondence, current eligibility or display. Supplied origins and dates are not authenticated.

Read the full guide
Performance and deployment 0 / 6 in scope
3 rules
Control summary · TS34

What this control is for

Field Core Web Vitals are documented and classified at the 75th percentile.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Missing CrUX data does not mean the page is fast.

Read the full guide
2 rules
Control summary · TS35

What this control is for

Laboratory tests support diagnosis rather than simulate field data.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

A Lighthouse score of 100 guarantees neither field CWV nor rankings.

Read the full guide
3 rules
Control summary · TS36

What this control is for

Monitoring connects Search Console, logs and deployments to decision dates.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Temporal correlation is not sufficient to attribute a traffic change.

Read the full guide
3 rules
Control summary · TS37

What this control is for

HTTPS, HSTS and embedded resources create neither certificate errors nor mixed content.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

HSTS strengthens transport after the policy is received; it fixes neither an invalid certificate nor a poor URL architecture.

Read the full guide
3 rules
Control summary · TS39

What this control is for

The CDN, Vary and geolocation do not serve contradictory SEO signals.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

First bounded profile with one canonical member per cell and reuse without transformation. Supplied reviews, sources, regions, clocks and logs are not authenticated; no general cache simulation. Two points do not cover all POPs/routes, and C does not establish actual Googlebot access.

Read the full guide
3 rules
Control summary · TS41

What this control is for

Critical SEO invariants are replayed automatically before and after deployment.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

First strict native TSEP profile without overrides; supplied commands are never executed. Reviews, completeness, clocks and runner are supplied, not authenticated. C qualifies the declared process, not global SEO health, causality or remote CI.

Read the full guide
Agents and crawling 0 / 2 in scope
3 rules
Control summary · TS42

What this control is for

Each automated agent is governed according to its documented purpose.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

Supplied scope and bounded robots profile; no automatic registry. Sources, reviews and decisions are unauthenticated; no inferred visit, real identity, operator compliance, indexing or citation.

Read the full guide
3 rules
Control summary · TS43

What this control is for

Access for authorized crawlers is tested with the full user-agent string and reconciled with logs.

Evidence to gather

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

Limits to keep in mind

First profile: assessor-initiated test client; no actual visit, identity, security or operator access inferred. Sources, logs, reviews and receipt are unauthenticated.

Read the full guide

30 readings available today

Renews:

Your daily limit: 30 readings

How it works

One reading checks your page and a few public sources. The allowance applies to your visitor workspace; additional protections apply to the shared network and the service as a whole.

Answering questions, viewing saved work and exporting results do not consume readings. These steps remain available when the allowance is used.