An indexing routine for a small portfolio of websites
Keep separate sites comparable without pretending they share one search identity.
A portfolio needs boundaries
Consider a founder managing a main company site, a product site and an independent publication. Each publishes at a different pace, and each has its own hostname and audience. This is an illustrative portfolio, not a reported customer outcome. A single total of indexed pages would hide the differences that matter when something stops working.
Begin by assigning every site a canonical origin, a responsible person and a publishing route. A subdomain may share a parent brand without sharing its deployment, robots rules or Search Console property scope. Keep these identities explicit so a repair aimed at one product does not accidentally change another.
Use a common evidence shape
A consistent report can contain site origin, observation time, pages sampled, HTTP results, directives, canonical observations and unresolved issues. That structure makes comparisons possible without inventing a universal health percentage. Twenty pages sampled on a 20-page site means something different from twenty sampled on a publication with thousands of URLs.
Record discovery and indexing evidence separately. A successful sitemap request belongs in one column; a Search Console inspection belongs in another. An IndexNow response is a notification event. Keeping the event types distinct prevents a busy founder from mistaking operational activity for a confirmed search outcome.
Review by publishing event
A new article needs a page-level check and a discovery route. A template update needs a sample across affected page types. A domain move needs a wider migration plan. The event determines the scope. This is more useful than running the same small sample after every change and assuming it proves the whole portfolio healthy.
Keep a short weekly exception review. Look for repeated failures caused by shared components, such as a canonical generator copied between sites. Fix the shared source when appropriate, but verify each deployed site independently. A shared repository does not guarantee identical live environment settings.
Make the first version honest
Noor Indexer includes quick-start inputs for the main Noor site, Good Chaser and the Income site, but they are starting addresses rather than preloaded successful audits. Every report is generated on demand. Saving is explicit and local to the browser; there is no cloud portfolio database or automatic monitoring in the beta.
For now, export a report after a material release and label it with the site and date. A future private dashboard can consolidate those records once accounts, isolation and retention are verified. Until then, a small collection of clear evidence is more dependable than an impressive display filled with assumed statuses.
Technical references
Primary documentation checked for this launch. Examples are illustrative unless explicitly described otherwise.
Continue reading
10RSS or sitemap: which should your publication maintain?
Keep both when they serve readers and discovery, using one content source.
How to audit a sitemap without making it a bigger problem
Check the addresses you want discovered, rather than treating every URL as a candidate.