Written by DROPS.ST.
Check the exact pages you want customers to find, using Google's recorded indexing information and a live rendering test. Do not decide that a menu is invisible because it uses JavaScript, or assume that a page is indexed because it looks good in your browser. The evidence is what Google can access, render and select for its index.
DROPS gives customers a mobile shop with product information, a cart and a clear ordering route. For organic discovery, ask how the particular public pages are delivered and linked in your setup. A strong shopping experience and a verified search implementation work toward the same commercial goal: qualified visitors reaching useful products and completing orders.
Separate discovery, rendering and indexing
Discovery means Google found a URL. Rendering means it processed the page, including supported JavaScript, to see its content. Indexing concerns what it chooses to retain and potentially show in search. Success at one stage does not prove success at the next.
Google runs JavaScript and can use rendered content for indexing. Blocked resources, errors or content that only appears after unsupported interaction can still cause problems. Google's JavaScript SEO guidance explains why the actual rendered output matters more than a blanket claim about the technology.
An embedded menu also needs a specific diagnosis. Its host page, embedded document, links and canonical signals may have different roles. Evaluate those concrete details rather than treating every embedded menu as the same technical problem.
Choose a small, representative URL set
Start with an approved public category page, a product page and a useful service page. Copy their real customer-facing URLs. Avoid account pages, private-menu links or temporary URLs containing session details.
For each page, write down the job it should perform. The product page should show the intended product; the category should support browsing that group; the service page should answer a particular question. If every link opens the same generic menu address, ask how individual content is represented before claiming product-level search coverage.
The menu software requirements guide helps connect these questions to the merchant's wider buying decision.
Inspect the recorded and current versions
In Search Console, inspect a URL in your verified property. Review the indexed status, crawl information and Google's selected canonical. Then use the live test to inspect the current rendered output, resources and screenshot where available. The recorded version and live test answer different questions; the live result does not predict Google's final canonical choice. Google's URL Inspection documentation describes those distinctions.
Look for the product name, meaningful description, relevant price or availability information, and useful links in the tested output. A screenshot of the menu shell alone is not evidence that all product content was processed.
Turn the result into a specific next action
This illustrative worksheet keeps a developer conversation focused:
| Observation | Question to investigate |
|---|---|
| URL was not discovered | Is it linked from an accessible public page or listed appropriately in the sitemap? |
| Page returns an access screen | Is this intentionally protected, or the wrong public destination? |
| Product content is missing after rendering | Are resources failing or does content depend on an interaction? |
| Google selected another canonical | Do the pages duplicate content or send conflicting signals? |
| Page is indexed but gets few useful visits | Does it answer a real customer search and offer the right next step? |
Do not ask for all five fixes at once. Record the observed problem and resolve that specific cause, then inspect the same URL again. Indexing and ranking can take time and remain Google's decisions.
Judge the business destination too
A search visitor needs more than an indexed page. Check that the item is current, the description answers the buying question and the route into the cart is understandable on a phone. A page can receive search traffic and still frustrate the customer.
Use menu sessions and order data to distinguish browsing from completed business. Keep technical access checks separate from claims about sales performance.
Choose a shop people can use and inspect the pages search engines receive. See DROPS and bring three representative URLs to the discussion. Ask for evidence about their actual behavior, then judge the customer journey they support.