Check your sitemap and search discovery
A sitemap lists public URLs that search engines can discover. Pineapple generates the website sitemap from eligible published content; you do not need to write an XML file for ordinary pages.
A sitemap helps discovery. It does not guarantee that Google will index every listed page or rank it for a particular search.
Open your sitemap
After connecting your custom domain, open its public /sitemap.xml address. For example, if your website is https://www.example.com, open https://www.example.com/sitemap.xml.
Use the domain that actually serves your website. An editor URL or draft preview is not the public sitemap address.
Check a page you expect to find
Publish the page and open its public URL.
Confirm that it shows the intended content.
Open the page's SEO Settings and check search visibility.
Save any visibility changes.
Open the sitemap and look for the public page address.
Search-hidden pages are excluded from the sitemap. A draft without a published page is not a public sitemap entry. Page folders are organisational items and are not proof that a public article exists at the folder address.
Pineapple normalises index-style paths in public URLs. For example, an editor path ending in /docs/topic/index can appear publicly as /docs/topic. Search for the public address rather than assuming the editor path must appear verbatim.
Check robots.txt and indexing separately
Pineapple also serves /robots.txt on the public website. Open it on the same domain as the sitemap. The standard production file allows crawling of ordinary pages, excludes /api/, and points to the sitemap. Local development blocks crawling, so do not use a localhost result to diagnose the public website.
You do not need to create a normal page called robots.txt. For an individual page you want hidden from search, use SEO Settings → Page can appear in search engines. A robots.txt crawl restriction and a page's noindex setting do different jobs: blocking a crawler does not reliably remove an already-known URL from search.
If the public file looks wrong, give support the exact domain and file URL before adding custom code. Do not paste robots.txt rules into a page body or website script field. See Google's explanation of controlling what appears in Search.
Submit the sitemap to Google
Use Google Search Console for your verified website property. Submit the public sitemap URL using its Sitemaps report, then inspect any errors it reports.
For the exact current Search Console procedure, see Google's Build and submit a sitemap guide.
If a page is missing
Check publication, search visibility and the selected website or domain first. Open the URL directly: a missing page, blocked website or login screen is an access problem that adding a sitemap entry does not fix.
If the page is accessible but still absent, give support the public page URL and sitemap URL. Keep the existing page while investigating; creating a second page with similar content can make the problem harder to understand.
If a listed page is not in Google
A successful sitemap fetch means Google could read the sitemap. It does not prove the individual page is indexed. Inspect that page's URL in Search Console and read the reported reason.
Check that the content is useful, linked from relevant pages and different from other pages on the site. Keep public URLs stable when the topic stays the same. If you migrate a URL, plan its replacement and redirect separately.
See SEO settings for visibility and metadata, and Launch and go live for public-page checks.
