Creator GEO publishes guide pages directly onto your storefront — on your own domain, inside your own theme. Three small changes to your theme make those pages discoverable by search engines and by your customers.
This guide is for whoever manages your Shopify theme. You'll need Online Store > Themes > Edit code access and permission to edit your navigation menus. Budget about 20 minutes.
Before you start
Do this after Creator GEO is connected to your store and at least one guide has been published — the checks below need a live page to look at.
Your storefront also needs to be publicly accessible. If it's still behind a password, remove it before starting — a password-protected storefront blocks the app from confirming where your pages live.
Your guides live at /apps/creator-answers/ on your own domain, like this:
https://www.yourstore.com/apps/creator-answers/best-carry-on-luggage
Open any published guide from the Assets screen in Creator GEO to see yours.
Step 1 — Advertise the guides sitemap in robots.txt
Why
Your guide pages are already crawlable — Shopify's default robots.txt leaves the /apps/ path open to search engines, and we don't change that. What's missing is discovery: without a pointer, a crawler only finds a guide by stumbling across a link to it.
Creator GEO publishes a sitemap listing every live guide. Adding one line to your robots.txt tells search engines that sitemap exists, so they can find and re-check your guides directly instead of waiting to encounter them.
This is an accelerant, not a dependency. Your pages work without it. It just makes search engines find them sooner.
What to do
Shopify doesn't let you edit robots.txt directly — you override it with a theme template.
Go to Online Store > Themes, find your live theme, and click … > Edit code.
Look in the Templates folder for an existing
robots.txt.liquid.
If you already have one, do not replace it. Someone customized it for a reason, and overwriting it will undo their work. Instead, add only this single line to the end of the existing file:
Sitemap: {{ shop.secure_url }}/apps/creator-answers/sitemap.xml
If you don't have one, click Add a new template, choose robots.txt, and paste this in full:
{% for group in robots.default_groups %}
{{- group.user_agent }}
{%- for rule in group.rules -%}
{{ rule }}
{%- endfor -%}
{%- if group.sitemap != blank %}
{{ group.sitemap }}
{%- endif %}
{% endfor %}
Sitemap: {{ shop.secure_url }}/apps/creator-answers/sitemap.xml
That loop is Shopify's own documented pattern for preserving the defaults. Everything Shopify normally puts in your robots.txt renders exactly as Shopify maintains it, including future updates on their side. The only addition is the last line.
Note what this doesn't do: it names no crawler, blocks nothing, and narrows nothing. We're adding an advertisement, not changing your crawl rules.
How to check it worked
Visit
https://www.yourstore.com/robots.txtin a browser.Confirm your existing rules are all still there, unchanged.
Confirm there's now one new
Sitemap:line at the bottom.Click that sitemap URL. You should get XML listing your live guide pages. If you get a 404, see The sitemap URL 404s in Troubleshooting.
Don't skip that last click. A wrong sitemap line fails silently — nothing breaks on your storefront, search engines just never find the sitemap.
Step 2 — Add a Guides link to your footer
Why
This is the more important of the two discovery steps, and it does two jobs at once.
For search engines: pages that nothing links to are slow to get indexed and carry little weight, no matter how good they are. A footer link appears on every page of your store, which creates a path from your most-linked pages, to your guides hub, to every individual guide. That's how the guides inherit the authority your storefront has already earned.
For customers: traffic will be minimal, but customers looking for creator testimonials will be able to find useful content from footer.
What to do
Go to Online Store > Navigation.
Open your footer menu.
Click Add menu item.
Name it Guides.
For the link, paste the full URL:
https://www.yourstore.com/apps/creator-answers
One thing that trips people up: your guides won't appear in Shopify's link picker when you start typing. They aren't Shopify pages — they're served by the app at a path on your domain. You have to paste the full URL rather than select it from the dropdown.
How to check it worked
Open your live storefront and scroll to the footer. The Guides link should be there.
Click it. You should land on your guides hub, listing your published guides.
If the hub shows a 404, check whether you have at least one guide published. A store with no live guides has no hub yet — that's expected, not a fault. Publish a guide and check again.
Step 3 — Confirm page titles are working
Why
Each guide page supplies its own title and meta description, and hands them to your theme to render. Most Shopify themes pick these up automatically, because we use the same standard variables Shopify's own pages use.
But themes vary, and a heavily customized one may not. When it doesn't, every guide page shows the same generic title — usually just your store name. That's a real problem: search engines treat duplicate titles across pages as a quality signal against you, and the title is the headline someone sees in search results. It's worth 30 seconds to check.
How to check
Open any published guide on your live storefront.
Look at the browser tab.
If the tab shows the guide's own title, you're done — no change needed. Skip the rest of this step.
If it shows your store name, or something generic that's the same on every guide, your theme needs a one-line fix.
The fix, if you need it
In Edit code, open layout/theme.liquid and find the <title> tag in the <head>. It should render page_title, like this:
<title>{{ page_title }}</title>
If your theme hardcodes something else there, change it to use page_title. Themes normally already do this, so if it's missing, it was almost certainly a deliberate customization — check with whoever made it before changing it.
While you're there, confirm the meta description does the same:
{% if page_description %}
<meta name="description" content="{{ page_description | escape }}">
{% endif %}
Reload a guide page afterward and check the tab again.
Troubleshooting
The sitemap URL 404s
Almost always this means your store serves guides from a slightly different path than /apps/creator-answers/.
Shopify assigns this path when an app is installed. If another app on your store had already claimed the same name, Shopify silently adds a number to the end — so yours might be /apps/creator-answers-1/. It can also be renamed by anyone with admin access.
To find your real path, open any published guide from the Assets screen in Creator GEO and look at its URL. The segment after /apps/ is your path. Update your robots.txt line and your footer link to match.
A guide URL returns 404
Same cause — no app proxy is registered at that path. Check your real path as described above.
A guide URL returns a Shopify error page (500)
Different problem, and the distinction is useful. A 500 means a proxy is registered at that path but its destination failed. That's on our side, not your theme — contact us rather than changing anything.
The hub 404s
You have no published guides yet. Publish one and try again.
Every guide page has the same title
Step 3 — your theme isn't rendering page_title.
Changing the guides path later
Don't, unless you have to. Guide pages that are already published keep their original URLs permanently, so renaming the path breaks every live guide. If it must change, tell us first.
What you don't need to do
To set expectations, here's what's handled automatically:
Styling. Guide pages render inside your theme and inherit your fonts, colors, header, and footer. There's no stylesheet to install and no design work needed.
URLs. Page addresses are generated automatically from your primary domain — nothing to configure.
Search engine notifications. Publishing a guide notifies search engines directly. The sitemap in Step 1 is a complement to that, not a replacement.
Products. Your catalog syncs automatically when the app connects.