---
title: "Magento SEO"
description: "Magento SEO from ShoutRank. Layered navigation, store views, and indexers, so a large catalog does not index every combination."
canonical: https://shoutrank.com/magento-seo
markdown: https://shoutrank.com/magento-seo.md
---

# Magento SEO

Magento SEO from ShoutRank. Layered navigation, store views, and indexers, so a large catalog does not index every combination.
Magento SEO keeps store views, layered navigation, and product URLs aligned with the markets and categories you actually sell.

Magento will generate a lot of URLs if you let the indexers and the layered navigation run without a rule. Multi-store setups add a second copy of the catalog that may or may not be a real market. The platform is capable. The configuration is usually where the index breaks.

International store views belong with [international SEO](https://shoutrank.com/international-seo). The catalog logic belongs with [ecommerce SEO](https://shoutrank.com/ecommerce-seo). This page is Magento’s machinery.

ShoutRank does not guarantee a ranking or a citation.

## The problem

### Layered navigation is fully indexable.

Attribute combinations outnumber products. Crawl budget goes to grids.

### Store views duplicate a market.

Two views share a language and a currency and both claim to be canonical.

### Indexers and caches disagree with the template.

A canonical was changed. The public HTML still shows last week’s tag.

## How ShoutRank approaches it

We read store-view scope before we read keywords. A view that is not a real market is consolidated. Layered routes are noindexed or canonicalized using Magento’s own configuration, then verified on a fetched URL after reindex.

We do not add a third-party SEO suite until the native settings have been read.

## What the work includes

### Store-view map

Which views are real markets, and which should consolidate.

### Layered-nav rule

Attributes that may create a URL, if any.

### Indexer note

What must be reindexed before a change is visible.

### Fetched proof

Public HTML after reindex, not the admin preview.

## Process

### Discovery

List store views, languages, and currencies with the merchant.

### Audit

Crawl layered routes and duplicate views.

### Strategy

Decide consolidation before copy work.

### Implementation

Change configuration with the Magento team and wait for reindex.

### Monitoring

Fetch the public URLs. Reopen anything the cache held back.

### Optimization

Only then brief category copy for the views that remain.

### Reporting

The view map, the nav rule, and the fetched canonicals.

## Why ShoutRank

### Reindex is part of the fix

A change in the admin is not done until the public response changes.

### Real markets only

A store view is not created so a report can say the brand is global.

### Native config first

Extensions come after we know the core is not already fighting itself.

## How success is measured

Store views that match real markets.

Layered URLs out of the index, or canonicalized as specified.

Public HTML matching the admin after reindex.

A named client result is published when that client clears the figure. Until then the report is the measurement.

## Questions

### Do you support Adobe Commerce and open-source Magento?

The SEO questions are the same. Implementation depends on who can change configuration in that project.

### Can you fix a slow catalog?

We will flag templates and routes that multiply URLs. Performance engineering of the Magento stack is a separate brief with your developers.

### Should every attribute be a landing page?

No. An attribute earns a URL when people search that combination and you can say something the parent category does not.

## Related

- [Ecommerce SEO](https://shoutrank.com/ecommerce-seo): What the catalog is trying to rank for.
- [International SEO](https://shoutrank.com/international-seo): Store views that are actually other markets.
- [BigCommerce SEO](https://shoutrank.com/bigcommerce-seo): Facets on a hosted catalog.