Public access and search are separate
New pages are private and search discovery starts disabled. A public page can be opened by anyone who has its link. Enabling search adds eligible routes to pagesend’s sitemaps and permits indexing; it does not change the audience of a private or team page.
Disabling search asks search engines not to index the page. It is not access protection. Use private or team access when content should require authorization. Search engines may take time to remove previously indexed information, and already downloaded public files cannot be recalled.
Review the page’s search settings
- Open the page’s management settings.
- Review its title, description, language, and nested routes.
- Make the page public only if that is the audience you intend.
- Explicitly enable search visibility when you want it discoverable.
Editing metadata requires permission to manage the page. Changing search eligibility also requires permission to change its audience. A connected agent uses those same rules. Local and staging deployments normally disable indexing; the settings show when this deployment has indexing disabled.
Describe each route accurately
Use a specific title that identifies the page’s subject and a short description explaining what a visitor will find. Avoid repeating the same title across unrelated nested pages. Write natural descriptions for people, without keyword lists or claims the content does not support.
pagesend can use metadata from finished HTML files and supported SPA route declarations. Explicit route overrides take precedence over imported titles and descriptions. An explicit noindex instruction in the source remains respected. An interactive app should render meaningful content at each declared route, not only after a user clicks a control.
<html lang="en">
<head>
<title>Customer research: findings and next steps</title>
<meta name="description"
content="The findings, evidence, and decisions from our customer research.">
</head>
<!-- Include the complete page body and local assets. -->
</html>Keep one stable address
The canonical share address uses the workspace, page address, and nested path. A publication revision is never part of that share link. Use it when linking to the page; temporary content or preview addresses are not substitutes.
New visits resolve the current publication. Renaming and republishing do not reset saved data. Making the page private or deleting it removes it from further eligible discovery responses. Returning it to public requires a fresh search opt-in.
Understand what search engines decide
Your published page keeps its original design and sandboxed iframe. pagesend supplies metadata at the share address and supports Google’s embedded-content indexing mechanism for eligible public pages. Google must still be able to render the content and decide to index it.
Correct metadata and sitemap inclusion do not guarantee indexing, ranking, or a particular search snippet. Full-content behavior in other search engines is not implied. Search previews are an editing aid, not a promise of how a result will appear.
Start with clear, useful content. The guides for publishing HTML and sharing AI reports explain how to prepare it.