Nuvemshop (known as Tiendanube in Spanish-speaking markets) solves the hard part of opening an online store: checkout, payments, shipping, inventory and hosting. That leads many merchants to assume SEO comes ready too. Part of it does. The rest depends on what you fill in on the dashboard, the theme you picked and how many apps you installed over time.
This guide is for merchants with a Nuvemshop store who get few visits from Google. It is based on an audit we ran in September 2026 on a retail store in southern Brazil with about 700 products. The numbers quoted here come from that store; they are not market averages. They show where problems usually appear and what can be done about each one.
What Nuvemshop already does well
Before changing anything, it is worth knowing what the platform already handles. In the audited store, these points were working with no technical intervention:
- Automatic sitemap: the sitemap.xml file is generated and updated by the platform as you add products, categories and pages.
- robots.txt: the platform publishes a robots.txt that allows crawling of public pages and points to the sitemap.
- HTTPS and redirects: the certificate and the redirect from http to https (and between the www and non-www versions) work without manual setup.
- Title and description per product and category: each product and each category has its own title and description fields for Google.
- Infrastructure: you do not have to manage servers, security updates or database backups.
Point 4 is the most underrated. In the audited store, all 42 categories had unique titles and descriptions, written by hand. It was the best finding of the audit and shows that the dashboard works when someone takes the time to fill it in. The problems were elsewhere.
What usually holds back organic traffic
None of the problems below is exclusive to Nuvemshop. They show up on any hosted store platform, because they come from choices of theme, apps and content. But all of them were present in the store we analyzed.
1. Theme and app weight
PageSpeed Insights scored 43/100 on mobile, with an LCP of 12.2 seconds, and 35/100 on desktop. LCP is the time until the largest visible element on screen appears (usually the banner or the product photo). At 12.2 seconds, many mobile visitors give up before they see the store.
The cause was in the page itself: the home page had 3.3 MB of HTML and loaded 150 scripts. Inside the HTML there were about 120 embedded product data blocks, one for each item shown in the home page showcases. Every installed app (chat, reviews, pop-ups, tracking, extra showcases) adds its own scripts. None of this is visible to the merchant on the dashboard, but the customer's phone has to download and process all of it.
2. Generic home page
The home page title and H1 were just the brand name. For people who already know the store, that is fine. For people searching for the kind of product you sell, the home page says nothing. The home page is usually the page with the most authority in the store, and wasting its title on a single word is one of the most common and easiest mistakes to fix.
3. Missing local signals
The store had a physical address, but the Organization schema (the structured data that tells Google who the company is) had no address or phone number, and there was no LocalBusiness schema. For a store that also sells over the counter, this means Google does not connect the website to the physical shop through the page data.
4. Incomplete schema on products and blog
The Product schema was present, but without reviews and with an empty description. Blog posts had no Article schema. Incomplete structured data does not break the store, but it lowers the chance of showing stars, price and availability in search results, which is exactly what drives the click.
5. Thin content on category pages
Well written titles and descriptions help, but the category page itself is usually just a product grid. Without a paragraph explaining what is there, who it is for, how to choose and what the common questions are, Google has little text to understand why that page deserves to rank above competitors.
6. Crawling and indexing
On Bing, about 50 of the 750 sitemap URLs were indexed. And the Lighthouse crawlable-anchors audit was failing: some of the page links were not regular links with an address, which makes it harder for crawlers to follow the path to the products. Menus, filters and buttons that rely on JavaScript to navigate are the usual suspects.
The audit in one sentence
The store did well on what depends on filling in fields (the 42 categories with unique titles and descriptions) and poorly on what depends on technical decisions: page weight, structured data, local signals and crawlable links. It is the most common picture we find in hosted stores.
What you can fix, and where
The table below groups the fixes by where they are made. Impact is a qualitative estimate based on what we saw in the audit; the actual result depends on the niche, the competition and the store's history.
| What to fix | Where | Expected impact |
|---|---|---|
| Home page title and description with the product type | Dashboard (store SEO settings) | High |
| Product titles and descriptions without original text | Dashboard (each product listing) | High |
| Supporting text on main categories | Dashboard (category description) | High |
| Remove apps that do not sell | Dashboard (installed apps) | High on speed |
| Lighter images before upload | Before listing | Medium to high on speed |
| Fewer showcases and products on the home page | Dashboard (theme customization) | Medium to high on speed |
| Descriptive home page H1 | Theme code, if your plan allows it | Medium |
| Address, phone and LocalBusiness in schema | Theme code, if your plan allows it | Medium for stores with a physical shop |
| Description in Product schema and Article on posts | Theme code, if your plan allows it | Medium |
| Google Business Profile | Outside the store (Google) | High for stores with a physical shop |
Through the dashboard, without touching code
Start here, because there is no technical risk. Rewrite the home page title and description to include what you sell and, if it makes sense, the region. Review your best sellers: a title with the name customers use when searching, a description with sizes, material, use and frequent questions (do not copy the supplier description, which is identical in dozens of other stores). Write a short, useful text at the top or bottom of the main categories. Then open the list of installed apps and ask, for each one: does it generate sales or only scripts? An app nobody has used in months should go.
Through theme code, with caution
Some fixes (home page H1, structured data, how menu links are built) can only be solved in the theme code. Whether you can edit that code depends on your plan and on the theme you use, and the rules change over time; check the platform help center for what applies to your store. If you do edit it, back up the theme first, change one thing at a time and test on mobile and desktop. A bad theme edit can break the storefront or the checkout, and the damage shows up in sales, not in SEO.
An important warning: themes and apps are updated by their authors. Changes made directly in the code may be overwritten by an update, so write down everything you changed. To understand the technical fundamentals behind these fixes, see our technical SEO guide for 2026.
Local SEO for stores with a physical shop
If your store also serves customers in person, local SEO usually brings results faster than fighting for national terms. Three fronts:
- Google Business Profile: create or claim the profile, confirm the address, fill in hours, category, real photos of the shop and a link to the website. Ask in-store customers for reviews and reply to all of them, including negative ones.
- Same data everywhere: name, address and phone written the same way on the website, the footer, the Business Profile and social media. If the theme allows it, include this data in the schema (Organization with address and phone, or LocalBusiness).
- City pages only where delivery is real: if you deliver to or offer pickup in nearby cities, a page per city can make sense, as long as it has its own information (delivery time, pickup method, shipping, landmarks). Identical pages that only swap the city name are treated by Google as duplicate content and usually hurt more than they help.
If you have no physical shop and only sell online, do not make up an address or create pages for cities where you do not operate. The focus then shifts to strong categories and content that answers purchase questions.
How to measure without fooling yourself
Three free tools are enough to start:
- Google Search Console: shows which searches the store appears for, how often it is clicked and which pages are or are not indexed. Verification can be done through the domain DNS, which works on any platform. Submit the sitemap and follow the pages report.
- Google Analytics: separate organic from paid traffic and compare sales and revenue by channel. Organic traffic that does not sell points to the wrong page for the search, not to a lack of SEO.
- PageSpeed Insights: test the home page, a category and a product, always on mobile. Save the numbers before each change so you can compare afterwards.
It is also worth adding the store to Bing Webmaster Tools: it is free, can import data from Search Console and shows indexing problems Google sometimes does not (that is how we saw the gap between the 750 sitemap URLs and the roughly 50 indexed). Measure monthly, not daily: SEO fluctuates, and the trend matters more than one good or bad day.
30-day checklist
A work order that prioritizes what carries no risk and what usually brings the most results:
Week 1: diagnosis
- ✓ Verify the store in Search Console and Bing Webmaster Tools and submit the sitemap
- ✓ Run PageSpeed on the home page, a category and a product and write down the numbers
- ✓ List installed apps and what each one delivers
- ✓ List the 10 categories and 20 products that sell the most
Week 2: dashboard
- ✓ Rewrite the home page title and description with the product type
- ✓ Review titles and descriptions of the 20 main products, with original text
- ✓ Remove apps that do not generate sales
- ✓ Reduce showcases and the number of products shown on the home page
Week 3: content and local
- ✓ Write supporting text on the 10 main categories
- ✓ Create or review the Google Business Profile (if there is a physical shop)
- ✓ Standardize name, address and phone on the website and social media
- ✓ Compress and re-upload the heaviest images
Week 4: theme code and measurement
- ✓ Back up the theme before any change
- ✓ Adjust the home page H1 and structured data, if your plan allows it
- ✓ Run PageSpeed again and compare with week 1
- ✓ Check indexed pages and new searches in Search Console
Want a diagnosis of your Nuvemshop store?
We run the same audit described here: speed, structured data, indexing, content and local signals, with a list of what to fix through the dashboard and what requires code. Talk to us.
Message us on WhatsAppConclusion
Nuvemshop does not stop a store from showing up on Google. It delivers the foundation (sitemap, robots, HTTPS, SEO fields) and leaves to the merchant the decisions that weigh the most: how many apps to install, how much to put on the home page, how much text to write and how to show Google that there is a physical shop behind the website.
Start with the dashboard, measure before and after, and only touch the theme code with a backup. If your store also relies on paid campaigns, landing pages deserve the same care: see what makes a landing page convert. And if you prefer someone to run the diagnosis with you, learn about our websites and SEO work.
Frequently asked questions
Is Nuvemshop bad for SEO?
No. The platform delivers an automatic sitemap, robots.txt, HTTPS and title and description fields per product and category. What usually holds back organic traffic are choices made on top of it: heavy themes, too many apps, a generic home page, thin content and incomplete structured data.
Do I need to edit the theme code to improve SEO?
Not to get started. Titles, descriptions, category texts, removing apps and lighter images are all done through the dashboard. Fixes such as the H1 and structured data may require theme code, which depends on your plan and theme. In that case, back up first and change one thing at a time.
Why is my store slow on mobile if the platform is fast?
Because speed depends on what the page loads. In the store we audited, the home page had 3.3 MB of HTML and 150 scripts, with about 120 embedded product data blocks, and mobile LCP reached 12.2 seconds. Fewer apps, fewer home page showcases and lighter images are usually the first step.
Should I create a page for each city?
Only where delivery or pickup is real and the page has its own information, such as delivery time, shipping and pickup method. Identical pages that only swap the city name are treated as duplicate content and can hurt the store.
How do I know if the changes are working?
Write down the numbers before making changes (PageSpeed, indexed pages in Search Console, organic clicks) and compare month by month. In Google Analytics, look at sales from the organic channel, not just visits. Content changes usually take a few weeks to show up in search.
