When a product page is missing from Google, “not indexed” describes a status, not the cause. Google may not know the URL, may not be able to fetch it, may encounter a redirect or noindex directive, may select another canonical URL, or may decide the page adds too little distinct value. Inspect the evidence for the specific URL before changing settings. A request to index a page does not fix a technical issue or guarantee that it will appear.
This workflow is for Salla store owners and marketers, but many checks apply to other ecommerce platforms. Salla's current help article describes product-level SEO fields and sitemap submission; the exact controls depend on the store setup. Verify the public rendered page instead of assuming a setting name or saved value proves what Google can see. Salla: Improve store visibility in search engines, Salla: Product SEO controls, Google: Technical requirements, and Google: Request a recrawl.
Start with the exact URL Inspection result
In Search Console, inspect the full public URL of one affected product in the correct verified property. Record the indexed result first, then run the live URL test. These answer related but different questions: the indexed report describes what Google last processed; the live test checks what Google can access now. Save the inspection date, reported indexing state, crawl result, selected canonical when available, and any stated reason. Do not infer that every product shares the same issue from one example.
Confirm the tested URL is the final canonical product URL shoppers can open without signing in. Check for redirects, protocol or hostname variants, and accidental query parameters. Compare the URL in the browser, the product link in the store, the canonical tag, and the sitemap entry. A sitemap can help discovery, but submitting it does not guarantee crawling, indexing, or ranking. Google says an indexing request can take days or weeks and is not a guarantee.
Check access, response, and indexing directives
Open the page in a private browser window or an unauthenticated session. Confirm it loads successfully, presents the intended product rather than an error, and does not require a customer account. Review the final rendered HTML and response behavior using available diagnostics. Check whether robots.txt blocks crawling, whether a noindex directive is present, and whether redirects lead to the expected page. A blocked crawl and a noindex instruction are different conditions; do not remove either until you know whether it is intentional.
On Salla, review the product's visibility and SEO settings in the current merchant interface, then check what the public page actually outputs. Theme changes, product state, inventory, and platform behavior can affect the visible page. Do not make a broad template or URL change to solve one product's status without evidence.
Compare canonical, sitemap, and internal links
Check whether the page declares a canonical URL and whether that destination matches the product page you intend Google to index. A canonical is a signal, not a command. If it points to a category, another product, or a different URL variant, investigate why before editing. Make sure the sitemap uses the preferred URL and that the page is not a redirect or an intentional non-indexable variant.
Next, check whether a visitor and crawler can reach the product through ordinary store navigation: a relevant category, search-filter-free listing, or contextual internal link. Google recommends linking to important products with crawlable links; pages reachable only through a store's internal search may be harder for Googlebot to discover. Make sure the anchor and surrounding context identify the destination. Do not add sitewide links to every product as a reflex.
Check whether the page gives shoppers distinct information
A technically accessible URL may still not be selected for search. Compare the product page with other pages on the store and with the manufacturer's description. Does it include accurate specifications, variants, compatibility, availability, delivery or return details, and original information that helps a shopper decide? Are important details visible in the rendered page rather than only implied by a product image?
Do not add paragraphs just to make the page longer. Resolve missing or contradictory specifications, copied boilerplate, unavailable products, and thin variants according to the real product facts. If two URLs are actually the same item with no meaningful difference, review the intended canonical or variant structure rather than manufacturing separate near-identical descriptions. Search Console's status is evidence to investigate, not a verdict that a product is valuable or worthless.
Use a bounded troubleshooting sequence
- Record the exact URL, product status, and inspection date.
- Read the indexed report and run the live URL test.
- Confirm the public page loads and returns the expected content.
- Check crawl access,
noindex, redirects, and canonical signals. - Compare the preferred URL with the sitemap and internal links.
- Review whether the page provides accurate, distinct shopper information.
- Correct only the confirmed cause, then recheck the rendered page.
- Request indexing for an eligible individual URL only after the underlying issue is resolved; for many URLs, maintain a clean sitemap and wait for recrawl.
Record what changed and what evidence confirms it. If Search Console has not updated yet, note that Google may need to crawl again; do not repeatedly submit the same unchanged URL expecting it to move faster.
Short-video script: Diagnose before you request indexing
Hook: “A missing product page? ‘Not indexed’ isn't the diagnosis.”
Show: Search Console URL Inspection for one public product URL. Contrast the indexed report with the live URL test.
Explain: “Check access, noindex, redirects, canonical, sitemap, and internal links. Then review whether the page gives shoppers distinct, accurate information.”
Close: “Fix the cause you can verify. A recrawl request can help Google revisit a page, but it cannot guarantee indexing.”
Educational carousel: The product-page indexing checklist
- Cover: Product page absent from Google? Diagnose first.
- Inspect one URL: Use the exact public product URL in the correct Search Console property.
- Separate reports: Indexed status and live test describe different moments.
- Check access: Does the page load publicly with the expected content?
- Review directives: robots.txt,
noindex, redirects, and canonical. - Trace discovery: Sitemap plus a crawlable internal link from a relevant category.
- Review value: Accurate, distinct information that helps a shopper decide.
- Set expectations: A request may prompt a recrawl; indexing is not guaranteed.
Field experiment thread: Triage a small set of missing products
This is a proposed diagnostic exercise, not a report of indexing results.
1/ Choose a small, representative set of affected product URLs. Record why each matters and confirm each is intended to be publicly discoverable.
2/ Capture URL Inspection's indexed result and live test separately for each URL. Note the date and any canonical or crawl details shown.
3/ Verify the page loads publicly. Compare its final URL, response, directives, canonical, sitemap entry, and route from a relevant category.
4/ Review the actual product information for accuracy, completeness, duplication, and distinct shopper value. Do not use word count as a quality proxy.
5/ Group URLs by evidenced cause. Correct one cause in a controlled batch; do not change storewide URLs or crawler rules based on a single page.
6/ Re-test the live page, document the change, then monitor for a later crawl and index-state update. Report “not yet updated” or “inconclusive” when Google has not processed the change.
Tool-neutral prompt pack: Review an indexing diagnosis
Prompt 1 — Separate observation from cause
Given this Search Console URL Inspection output [paste], classify each statement as observed, inferred, or unknown. List plausible causes supported by the evidence and the next check for each. Do not claim a fix or guarantee indexing.
Prompt 2 — Compare page signals
Compare this public product URL [URL], rendered page details [paste], canonical [value], sitemap entry [value], and internal route [description]. Identify inconsistencies and missing evidence. Do not recommend changing a URL unless the evidence demonstrates a mismatch.
Prompt 3 — Product-page quality review
Using only these verified product facts [facts] and page text [text], identify missing, contradictory, duplicated, or unsupported claims that could prevent a shopper from making an informed decision. Propose corrections without inventing specifications or adding filler.
Stop-doing swipe file: Replace indexing shortcuts with diagnosis
Stop: “Request indexing again; that will make the product appear.”
Use: “Record the current inspection result, find and correct an evidenced issue, then request a recrawl if appropriate. Inclusion is not guaranteed.”
Stop: Removing noindex or changing robots rules before checking whether the restriction is intentional.
Use: Verify the public page's indexing directives and the business reason behind them before changing configuration.
Stop: Changing the product URL because the old one is not indexed.
Use: Compare the intended URL across the page, canonical, sitemap, and internal links first. Preserve established URLs unless a separate migration decision is justified.
Stop: Adding generic text to every product page to make it “longer.”
Use: Add or correct only useful, verified product details that help the customer decide.
Hook–Value–Template: Find the reason before taking action
Hook: “A missing result is a symptom. Which signal explains this URL?”
Value: Check the indexed report and live test, then trace access, canonical, discovery, and page usefulness. Fix one supported cause at a time and keep a record.
Diagnostic note: “URL: [exact URL]. Checked on: [date]. Indexed report: [observed state]. Live test: [observed state]. Access/directives: [evidence]. Canonical: [value]. Sitemap: [yes/no and exact URL]. Internal path: [source link]. Page information gap: [verified issue or none found]. Action: [specific correction]. Recheck: [date or pending crawl]. Outcome: [updated / unchanged / inconclusive].”
This template separates evidence from assumptions. It does not promise that a corrected page will be indexed or rank in Google.