A share button makes a report easy to send to a client. It also creates a publishing decision: should someone who has never used your tool be able to discover that report through search?

For a client deliverable, the answer is often no. For a reviewed public example with permission, it may be yes. Decide this before the tool starts producing URLs, rather than treating every successful report as a new SEO landing page.

On 26 October 2026, Google updated its user-generated spam guidance to address link-shared content and abuse monitoring. This was a documentation update, not an announced ranking update. Google's change log records the change and its purpose.

Which tool outputs should be public?

Google's spam-prevention guide now explicitly covers tools that publish shared pages, generated content and web apps. It asks platforms to consider whether outputs are intended for search discovery or direct sharing.

That distinction is useful for SEO tools, report builders and AI applications. My recommended starting point is a three-part inventory:

OutputIntended readerRecommended treatment
Client audit containing private informationAuthorised client and teamRequire access controls
Non-sensitive report shared for a particular taskPeople receiving the linkKeep out of search with a crawlable noindex response
Edited, permission-cleared demonstrationProspective users researching the problemConsider making it indexable after review

These are proposed product decisions, not a description of Fanout's current access controls or a universal Google requirement. A particular report can move between categories, but that transition should require a deliberate action.

What belongs in a public sample?

A raw export is written for the person who requested it. A public example needs enough context for a stranger to use it.

Before approving one, ask:

  • What question does this example help someone answer?
  • Which inputs were assessed, and when?
  • Which findings were checked by a person?
  • What does a score measure, and what does it leave out?
  • Does the example expose information the client did not agree to publish?

For an audit example, explain one recommendation all the way through: the observed gap, why it matters, the proposed edit and what evidence would show whether the edit helped. Remove unsupported recommendations rather than presenting the export as an authoritative checklist.

The Fanout build story follows that distinction between a generated question set and practitioner judgement. A public sample should make the judgement visible.

Test the whole report journey before release

A product review should cover the files and URLs a report creates, not only the first screen.

Consider an illustrative audit tool with a browser report, a PDF download and a duplicate link created when someone shares it. This is a fictional example, not an account of a Fanout deployment.

The team marks the browser report noindex. But the PDF still opens without restrictions, and regenerating the report creates another public URL. The first check passed; the report journey did not.

Use a small release test matrix:

TestEvidence to record
Open the report while signed outWhether the intended access restriction actually applies
Inspect the HTML and response headersThe indexing instruction served by the live route
Open each export directlyWhether the export follows the same intended policy
Regenerate, share and revoke the reportWhich new URLs appear and which old links still work
Publish an approved demonstrationWhether review changes only the intended sample

Give each failure an owner. A developer can confirm the response; the person responsible for client permissions must decide whether the content can be public. Neither decision substitutes for the other.

Measure the URLs you intended to publish

Google recommends watching Search Console for unexpected indexed pages, impressions and queries, alongside platform creation patterns. Those signals can help identify abuse; they do not prove it on their own. Monitoring guidance

For a tool team, I would maintain a simple reconciliation: reviewed public examples, share-only outputs and restricted reports. Compare unexpected search appearances with that inventory. A client report appearing in search is a different problem from a public guide struggling to get indexed.

Start with one real report journey this week. Record every URL it creates, assign an intended audience, and test whether the implementation matches. Then choose one permission-cleared example worth editing for public discovery.

Need help making that decision for your tool or reporting workflow? Book a discussion and bring one example output. We can scope the technical and editorial checks it needs.

Sources checked on 29 October 2026. The report journey is illustrative. The release matrix is a recommended workflow; no client results or ranking improvements are claimed.

Vishnu Sudevan

Senior SEO, AEO & GEO consultant and practitioner. I write about search strategy, the tools I build and lessons from hands-on work.

More about my work →

Need help with a wider search challenge? Explore SEO consulting.