- Where it is
- Health check
- Pages
- robots.txt, llms.txt and sitemap.xml
- Where to find llms.txt, robots.txt and sitemap.xml
- IndexNow
- Business & schema
- Crawlers and Get found
- Framework tips
Where it is
Cloud Ninza dashboard → Marketing → Marketplace → choose the project (and the website, if it has several). Search Master is included with Growth, Business and Pro plans of static, PHP, Node.js (Next.js, NestJS, Express), Python (Django, Flask, FastAPI) and Java (Spring Boot, Tomcat) hosting.
1. Health check
Press Check my website. In about a minute our server reads your live site like a search engine and an AI crawler: robots.txt, sitemap.xml, llms.txt, the IndexNow key, your home page’s title, description, canonical, Open Graph and schema, then up to 40 pages from your sitemap. You get a score out of 100 and a list of what to fix. Run it again after every deploy that changes pages.
2. Pages
Every page checked, with its own score and the exact problems: missing or duplicate title, description too short or long, no H1 or several, images without alt text, thin content, no structured data, blocked by robots, not in the sitemap. Fix them in your code (titles and descriptions live in your framework’s head / metadata), deploy, and check again.
3. robots.txt, llms.txt and sitemap.xml
The robots.txt · llms.txt · sitemap tab shows your site’s live files. For each one you can:
- Keep mine — if your app already serves a good file, nothing changes.
- Keep mine and add what is missing (robots.txt) — adds the crawlers and the Sitemap line yours lacks.
- Generate — Search Master writes one from your pages and business details; edit it and Save.
- Saved files are served by the web server in front of your app at
/robots.txt,/llms.txt,/llms-full.txtand/sitemap.xml. Your code and Git releases are never touched; Stop serving gives the address back to your app.
Where to find llms.txt, robots.txt and sitemap.xml
- Your live files are always at
https://yourdomain.com/llms.txt,/robots.txtand/sitemap.xml(and/llms-full.txtonce you save one). - A file you Generate or Save in the dashboard is stored in
web/yourdomain.com/private/cn-seo/(visible in the File manager) and answered by the web server in front of your app — so it works the same for Next.js, Node.js, Python, Java, PHP and static sites, and survives every deploy. - If your own code or
public/folder already serves one of these addresses and you choose Keep mine, yours is the one served; edit it in your project as usual. - Stop serving removes ours and gives the address back to your app.
4. IndexNow
Search Master creates your IndexNow key and serves the key file for you. Send all pages submits every URL in your sitemap to Bing and the other IndexNow engines; send again after each release. The log shows each answer (200 or 202 = accepted).
5. Business & schema
Fill in your business name, logo, description, phones, emails, offices and up to 25 social profiles. Search Master writes them into llms.txt and gives you ready Organization / LocalBusiness JSON-LD to paste once into your layout (for example in Next.js app/layout.tsx, a Django base template, a Thymeleaf or JSP layout, or your static index.html). The FAQ schema maker turns questions and answers into FAQPage JSON-LD for any page.
6. Crawlers and Get found
Crawlers lists every search engine, AI assistant and SEO tool your robots.txt allows or blocks. Get found gives the steps for Google Search Console, Bing Webmaster Tools and Brave, and links to site: searches so you can watch your pages appear.
Framework tips
- Next.js: render pages on the server (App Router server components or
getStaticProps/SSG), setmetadataper page, and avoid pages that are empty until JavaScript runs — crawlers and AI fetchers often do not run it. - React / Vue / Angular single-page apps: pre-render (Vite SSG, Astro, Nuxt, Angular SSR) or at least serve real HTML for important pages.
- Django / Flask / FastAPI: one
<title>and<meta name="description">per view,django.contrib.sitemapsor your own sitemap, canonical tags in the base template. - Spring Boot / JSP: put title and description in the model for each controller and render them in the layout; return real 404 status codes for missing pages.
- Static sites: one HTML file per page with its own title and description; use clean addresses (
/aboutservesabout.htmlon Cloud Ninza).
Stuck? Our engineers answer support tickets around the clock. Contact us, or create an account and open a ticket from the dashboard — the same guides are there too.