# TractionScout search-readiness investigation

On October 2, 2026, a public HTTP inspection of TractionScout found readable
homepage, documentation, and workflow HTML, alongside blog canonical and
missing-page response problems. These are technical observations of the
served site before the proposed fixes. They do not establish rankings,
search traffic, AI citations, or customer conversion outcomes.

## What was observed

The inspection used ordinary public GET requests and parsed the returned
HTML and XML. No private Search Console or customer records were accessed.

| Public surface | Observation on October 2, 2026 | Reviewable follow-up |
| --- | --- | --- |
| [Homepage](https://tractionscout.com/), [overview](https://tractionscout.com/docs/overview.html), and [signup workflow](https://tractionscout.com/workflows/posthog-stripe-readout.html) | HTTP 200 with substantive readable content, English language declaration, and HTTPS canonical URLs | Preserve server-readable answers and verify generated metadata after changes |
| [Main sitemap](https://tractionscout.com/sitemap.xml) | 28 URL entries | Keep published guides discoverable and include only intended canonical pages |
| [Blog](https://tractionscout.com/blog) | HTTP 200 with a German empty article placeholder; canonical used HTTP despite an HTTPS request | Serve a useful index with the intended locale and HTTPS canonical |
| [Blog sitemap](https://tractionscout.com/blog/sitemap.xml) | One HTTP URL for the blog | Make its locations agree with the served canonical URLs |
| An unknown extensionless route | HTTP 200 with the homepage title, content, and canonical | Return a real missing-page status without breaking known application routes |

The hostname, tested paths, observation date, response status, and parsed
metadata define the scope. A few inspected pages cannot establish every
route's behavior or Google's indexed version.

## Reproduce the public checks

Use a normal HTTP client, follow redirects, and preserve response headers
with the observation timestamp. These commands read public content:

```sh
curl --location --dump-header - --output /dev/null https://tractionscout.com/blog
curl --location --dump-header - --output /dev/null https://tractionscout.com/blog/sitemap.xml
```

For canonical, locale, and sitemap checks, parse HTML and XML rather than
matching an assumed serialization. This Python example reports the selected
pages without submitting credentials or changing the site:

```python
from html.parser import HTMLParser
from urllib.request import urlopen
import xml.etree.ElementTree as ET

class Metadata(HTMLParser):
    def handle_starttag(self, tag, pairs):
        attrs = dict(pairs)
        if tag == "html":
            print("language:", attrs.get("lang"))
        if tag == "link" and "canonical" in attrs.get("rel", "").split():
            print("canonical:", attrs.get("href"))

origin = "https://tractionscout.com"
for path in ("/", "/docs/overview.html", "/blog", "/sitemap.xml",
             "/blog/sitemap.xml", "/not-a-real-page-traction-audit"):
    with urlopen(origin + path, timeout=30) as response:
        body = response.read().decode("utf-8")
        print(path, response.status, response.url)
        if path.endswith(".xml"):
            locations = ET.fromstring(body).findall(".//{*}loc")
            print("sitemap URLs:", len(locations))
            print("non-HTTPS URLs:", [e.text for e in locations
                  if not (e.text or "").startswith("https://")])
        else:
            Metadata().feed(body)
```

After a missing-page fix, that probe should raise an HTTP 404 error in
`urlopen`; record the status as the expected observation rather than treating
it as a failed site check.

## What would count as a result?

Review the concrete content and routing changes locally, then verify the
actual served responses after an authorized deployment. A generated file
does not prove deployment, recrawl, indexing, ranking, or citation.

Use an authorized Search Console property to establish search performance
and index coverage separately. Follow qualified activation only when
recorded identities and cohorts support it. No search or conversion lift
is claimed by this investigation. See
[measurement methodology](/docs/measurement-methodology.html) and the
[Search Console workflow](/workflows/search-console-content-experiment.html)
to prepare a baseline and evaluate a later content experiment.


Maintained by TractionScout · Reviewed 2026-10-02 · Updated 2026-10-02


## Setup guides

- [Set up your project](https://tractionscout.com/docs/getting-started.html)
- [Check Search Console availability](https://tractionscout.com/docs/integrations.html)

## Start with this question

Why do people see us on Google but skip us?

[Improve my Google clicks](https://tractionscout.com/signup/tractionscout?workflow=search-console-content-experiment)

Your question is carried into setup. Review it, connect the data you need, and send it to Scout when you are ready.

## Related examples and guides

- [Help the right people click your Google result](https://tractionscout.com/workflows/search-console-content-experiment.md): See the searches that show your pages but bring few visits, then review a title and description that better explain what is on the page.