November 2, 2026 · The lunalink.ai team

Should Shopify merchants test public pages before installing another app?

Hands typing on a laptop with an e-commerce website open, showcasing online shopping. — Photo by Shoper .pl on Pexels

You notice a store problem and the usual answer is to install something.

Maybe products are hard to find. Maybe search traffic is flat. Maybe you want AI assistants to understand your catalogue better. An app might help, but it is rarely the first thing to do.

First, look at your store as a visitor does: logged out, with no admin session, no preview link, and no special access.

That view is where customers start. It is also where search engines and other systems begin reading your store.

At Lunalink, we built our free scanner around that idea. It reads public URLs only: `robots.txt`, the catalogue information it can reach, product markup, and policy pages. There is no install and no login. A merchant should not have to trust a stranger’s app just to learn the basics about what their storefront shows.

The useful question is simple: is the problem already visible on the public store?

If it is, you can often identify the next step before adding another app and another permission request.

Start in an incognito window

Open an incognito or private browser window. Do not log in to Shopify. Then visit your homepage and a few key pages.

This matters because your admin session can hide problems. You may see a theme preview, an account state, or a page variation that ordinary visitors do not.

It also gives you a quick check for a more basic issue: whether the storefront is public at all.

Shopify says that when a store is password-protected, online-store pages are hidden from visitors and search engines. Its sitemap is not available to search engines while the store is private.

You can check this in under a minute:

Open your homepage in an incognito window.
Make sure it does not show a password page.
Open a product page from a search result or direct link.
Check that the page you see is the page you expect customers to see.

If the store is private, fix that before spending time on crawler settings or installing an SEO app. There is little value in improving pages that visitors and search engines cannot reach.

Read the files your store already publishes

Shopify creates some useful public files for you. They are not exciting, but they tell you a lot.

Check `robots.txt`

Open:

`yourstore.com/robots.txt`

Shopify generates a default `robots.txt` file. Its documented rules allow public product, collection, page, blog, and policy content. They disallow areas that should not be public crawl targets, including `/admin`, `/cart/`, `/checkout`, `/account`, and `/orders`.

You do not need to understand every line. Start by looking for changes that do not make sense for your store.

For example:

Is a product or collection path blocked?
Is there a rule you do not recognise?
Did a past theme edit add a custom robots template?
Does the live file match what you thought you configured?

Be careful with custom edits. Shopify lets merchants create `templates/robots.txt.liquid`, but that replaces Shopify’s generated output. Shopify warns that incorrect edits can reduce traffic.

There is another reason to inspect the live file rather than trust a template. Shopify has acknowledged an investigation into a report that `robots.default_groups` returned an older rule set than the managed `robots.txt` served by Shopify. The practical lesson is not to panic over every difference. It is to check the URL that crawlers actually receive.

Also, `robots.txt` is not a single switch for all AI-related commerce activity. Shopify says its robots and network controls affect open-web discovery. Product data sent through Shopify Catalog to activated agentic storefronts is controlled separately.

That distinction matters if you are trying to answer a specific question. “Can this crawler discover my public pages?” and “Can an agentic storefront use Shopify Catalog data?” are not the same question.

Check `sitemap.xml`

Open:

`yourstore.com/sitemap.xml`

Shopify automatically generates this file and updates it when products, collections, webpages, blog posts, or primary product images change.

You are not auditing every URL by hand. You are looking for obvious gaps.

Try this:

Search the page for the handle of a current product.
Search for an important collection.
Check whether a recent page appears.
Open one listed URL and make sure it loads without a login.

If a product is missing from the sitemap, do not assume an app is the fix. Check whether the product is actually published to the Online Store sales channel first. Check the product’s status. Then check the live product URL.

The public storefront is often enough to narrow down where the issue lives.

Do not rely on an undocumented catalogue shortcut

You may see advice to open this URL:

`yourstore.com/products.json?limit=250`

Treat that advice carefully.

Current Shopify documentation does not establish this as a documented public catalogue API for a store audit. Shopify’s documented Admin REST products endpoint requires authentication. The Storefront API also uses a token.

That does not mean public catalogue information is useless. It means you should not build an important check around an endpoint you have not confirmed for your own store.

Use pages that you know visitors can reach instead:

Product pages
Collection pages
Search results
Your sitemap
Navigation links

If you need complete product data for operations, reporting, or a custom integration, that is the point where authenticated Shopify access or a suitable app may be the right answer.

Turn JavaScript off for one product page

Pick a product page and disable JavaScript in your browser. Then reload it.

You are not expecting the page to look perfect. You are checking whether its basic meaning survives.

Can you still see:

The product name
A useful description
The price
Variant or size information
Product images or image text
A clear path to the rest of the store

Google can process JavaScript for pages in its rendering queue. But Google also recommends server-side rendering or pre-rendering where possible, and notes that not all bots can run JavaScript.

This is why a no-JavaScript check is useful. A page that depends on a script to reveal its only product description has a fragile foundation.

You may find that nothing is wrong. That is useful too. You have ruled out one reason to change the theme or install a script-heavy app.

Read your policy pages like a customer would

Next, open your public policy pages. Common Shopify policy URLs include:

`/policies/refund-policy`
`/policies/privacy-policy`
`/policies/terms-of-service`
`/policies/shipping-policy`
`/policies/subscription-policy`

Your store may not use every one.

Read the ones you do publish and ask plain questions:

How long does shipping take?
Where do you ship from?
What is the return window?
What condition must an item be in for return?
How does a customer contact you?
Is the business identity clear?

Shopify says policy pages are public. Its terms also require public-facing business contact details, including a business name, email, phone number, and physical address.

Do not send customers hunting through a footer, an automated email, and a social profile to answer one basic question. Put the answer on the relevant page.

Then check your contact page. Shopify themes include a built-in contact form through the `page.contact` template. If you only need a straightforward public Contact Us page, you may not need an app for it.

When an app is actually the answer

A public audit is not an argument against apps. It is a way to give them a clear job.

An app is useful when it needs to do something that a browser check cannot do, such as:

Change storefront content or theme behavior
Monitor pages over time
Alert you when something changes
Connect to private Shopify data
Run a workflow that would otherwise be manual

Start with the visible problem. Then choose the smallest tool that solves it.

If your product page has thin specs, write the missing specs. If your shipping policy does not answer delivery questions, update the policy. If the contact page is missing, add one through your theme.

Install something when the work needs ongoing automation, private data, or a store change you cannot reasonably manage yourself.

Sources

Open an incognito window this week and check one product page, `robots.txt`, `sitemap.xml`, and your shipping policy. Write down what is unclear before deciding what to install.

shopifystore audittechnical seostorefront