SEO Revolution: setup and help

Back up the database, current SEO settings, route rules, root robots.txt and generated files. Upload and install mprseorevolution, then click Configure to open SEO Revolution > Dashboard. Run Tools > Integrity Check before configuring a live output.

Select one shop before saving shop-specific SEO settings or policy overrides. Review Back Office employee permissions if a staff account can view a page but cannot save it. Installation grants access to the authenticated installer's profile; later menu repairs do not grant every employee access.

The menu separates Redirections, Technical SEO, Content, Linking, Indexing, Tools, Settings and Global Settings. Start with metadata for one page, then add the other outputs you need. Use one owner for each canonical, hreflang, structured-data, sitemap and tracking output.

Open SEO Revolution > Global Settings. The Settings menu entry opens the same form. The values below are the form's defaults; a shop with saved settings keeps its own values.

General

• Enable SEO Revolution. Form default: 1. This switch is saved but does not currently turn the storefront output on or off. To stop SEO changes and keep only tracking, turn SEO Features off; to stop everything, disable the module in Module Manager.

• Trailing Slash Handling. Saves your preference for no change, adding or removing a trailing slash. Default: none. This field does not change canonical URLs. Configure that behavior in the shared canonical settings and check redirects separately.

• SEO Features. Default: on. Turn this off if the module should run tracking only. The module then skips its SEO output, route, redirect and file changes while retaining configured Google tracking/uploads. Clear the page cache after changing it.

• Friendly photo deep-link URLs (/product/photo/N). Default: off. Enable only when you intend this module to own these routes. With it off, image deep links use query parameters.

Sitemap generation, robots.txt publication, SEO policy rules and some redirects start disabled on a new installation. These tasks keep existing files while disabled. Global Settings has no switch to activate them. Check the task results before using their output.

External Links and Pagination

• Add nofollow to external links. Default: 1. The setting is saved, but the module does not currently rewrite external links, so no nofollow is added.
• Open external links in new tab. Default: 1. The preference is saved, but it does not make external links open in a new tab.
• Add noopener to external links. Default: 1. The setting is saved, but the module does not currently rewrite external links, so no noopener is added.
• Whitelist domains. Stores the domain exceptions for the global form preferences. Default: empty. Enter one domain per line.
• Add rel="next/prev". Form default: 1. This global preference is saved but does not control pagination links. Check the links on later pages.
• Canonical to first page. Stores the first-page canonical preference. Form default: 0. Verify it against shared canonical and entity pagination settings.
• Noindex paginated pages. Stores the global later-page noindex preference. Form default: 0. Use SEO Policies and inspect effective robots output.

Several fields on this form are saved but do not change the storefront: Enable SEO Revolution, Trailing Slash Handling, the External Links and Pagination switches, Enable hreflang, the Open Graph and Twitter fields and the Schema.org switches. Change those outputs on their own pages (Open Graph & Social, Structured Data) and check the public page after saving. To stop all SEO output and keep only tracking, turn SEO Features off.

Open Graph / Social and Monitoring

• Enable Open Graph tags. Form default: 1. This field is saved but not read by the storefront. Open Graph output follows the Enable Open Graph switch on the Open Graph & Social page, which is on (1) after installation.
• Enable Twitter Cards. Form default: 0. This field is saved but does not turn Twitter Cards on or off. Twitter Cards start enabled (1) after installation.
• Twitter handle. Initially empty. The value is saved, but it does not populate the twitter:site tag. No form supplies the separate value used for that tag, so it is absent with the default configuration.
• Default social image. Uploads the fallback image used when a page has no specific Open Graph image; default: ``.
• Ignore exploit probes. Stops obvious scanner and malformed URLs being stored in the 404 monitor; default: 1.
• Ignored 404 URL patterns. Adds custom substring, wildcard, or regex: ignore rules for the 404 monitor; default: ``.

Maximum stored 404 rows defaults to 10000. 404 retention days defaults to 0, meaning no age cutoff. Set these to bound your monitoring data. The default exploit-probe filter is on; Ignored 404 URL patterns accepts the supported substring, wildcard and regex: rules.

The global form still exposes Enable Schema.org markup, Organization Schema, WebSite Schema, Product Schema and Include Reviews in Product Schema. Their listed form defaults are on, on, on, on and off respectively. Configure effective shared structured-data settings under Content > Structured Data and inspect readiness there; do not treat a legacy global switch as the full shared configuration.

Use Content > Meta Tags to review missing or unsuitable titles and descriptions. Edit an individual page's Meta title and Meta description when it needs explicit text. Use the entity-type template editor for repeatable title, description, H1, URL, Open Graph, custom head and pagination templates. Product, category, CMS, manufacturer and supplier contexts have different variables.

For products, you can use:

%product_name% | %product_brand% | %shop_name%
Buy %product_name% in %product_category% from %shop_name%. Price: %product_price%.

For category pagination:

%category_name% - Page %page_number% | %shop_name%
Browse %category_products_count% products in %category_name%. Page %page_number%.

Use Bulk Operations when you need to apply reviewed changes at scale. Test one entity first and inspect its final title, description and H1. Do not assume a saved draft or template has already replaced native metadata.

The module stores per-page canonical, robots, Open Graph, custom-head and redirect information through its page registry and related editors. Use the appropriate page editor for its entity type. Keep custom head code limited to output you intend to publish.

Developers can read the registry from another module:

require_once _PS_MODULE_DIR_ . 'mprseorevolution/vendor/autoload.php';
$registry = new \MPRSEORevolution\Classes\Registry\PageRegistry();
$productPages = $registry->getPagesByType(
    \MPRSEORevolution\Classes\Registry\PageRegistry::TYPE_PRODUCT
);

Use Technical SEO > Canonical Rules for the shared canonical configuration. The canonical package defaults to enabled, lowercase on, forced trailing slash off and pagination stripping off. Its tracking-parameter list is:

utm_source,utm_medium,utm_campaign,utm_term,utm_content,fbclid,gclid,msclkid

By default, each paginated page uses its own canonical URL (self). Review canonical behavior on page one, later pages, URLs with tracking parameters and product combinations. A link in HTML should resolve to the intended canonical page without an unexpected loop.

Open Hreflang > Configuration and Hreflang > Groups. These are shared with Hreflang Manager. Configure the active languages, automatic/manual connections and x-default choice there. The old two-line global hreflang preference list does not describe this current screen. Test actual alternate links in each shop/language and avoid listing unpublished translations as usable alternates.

Open Technical SEO > SEO Policies for page-type defaults and per-module overrides. Choose one shop before saving the matrix. Use inherited choices until you need an explicit Index/Noindex or enabled/disabled policy. Check the final robots meta/headers, canonical and sitemap inclusion together.

Open Redirections > Redirects. Create a rule with Source URL, Target Page, Redirect Type, optional Note and Active. The form offers 301, 302 and 410. Leave the target empty for 410 Gone. Test source and destination before applying a broad rule.

Redirects and 404 monitoring start enabled (1). Global Settings has no separate controls for them. 404 Monitor records missing front-office requests with URL, referrer, user agent, IP, hit count and resolved state, subject to exclusions and limits. Trigger a harmless missing test path and inspect its record.

Use Redirections > Retired Products for the available product lifecycle workflow. Inspect its status when enforcement is inactive.

Open Technical SEO > Robots.txt. Review user-agent rules and preview generated content before publishing. The manager can back up a previous root file and offers restoration/default-generation operations. Keep a separate backup of your original root file.

Generated content can include user-agent rules and a sitemap reference. Use the actual sitemap URL your shop serves. Do not paste a sample path list over an existing live file without reviewing the shop's own paths and the module's current publication status.

Check that the web process can write the intended root file and backup location. If publication is skipped with enforcement_off, inspect the deployment's enforcement state. Verify the HTTP response at /robots.txt after a save. Blocking a URL from crawling can prevent a crawler from seeing metadata on that page.

Open Technical SEO > Sitemap, then Sitemap Settings. Use its URLs/logs screens to inspect generated output and validation.

Content and formats

Products, Categories, CMS Pages, Blog Posts, Filter SEO Pages, Search SEO Pages, core pages, module pages, images and hreflang default on. Manufacturers and Suppliers default off in the sitemap settings. Blog/filter/search content needs the corresponding installed provider. Pages added by other modules controls the additional provider group, with separate provider choices for FAQ, documentation, knowledge base, showcase and similar pages.

Initial Priority & Frequency values are:

Include image sitemaps, Include hreflang links, Split into multiple files and Generate HTML sitemap default on. Max URLs per file defaults to 50000. Generate RSS feed defaults off. Keep splitting on for a large catalogue and inspect the index as well as child files under /sitemaps/.

Verification and submission

Submit sitemap to Google Search Console and Legacy Bing sitemap ping both default off. The Google action uses an authenticated Search Console connection. Do not rely on anonymous ping endpoints. First generate and inspect the files, then submit the verified sitemap through the configured connection or your webmaster tools.

The module provides a sitemap URL. Use the actual index URL shown/generated by your installation, including shop paths. A skipped cron generation can indicate inactive enforcement; check the result instead of assuming the file was refreshed.

Open Content > Structured Data. Its tabs are Schema types, Organization, Social profiles, Products, Shipping, Returns and Additional types. The page shows readiness and uses shared settings. When older settings are imported, existing saved settings take precedence; imported values can remain in use.

If no saved settings override them, SEO Revolution starts with a product image limit of 30, product weight unit KGM, variant limit 50 and category product limit 12. WebSite search, shipping and automatic microdata/JSON-LD cleaning start off. The shared form can have different initial values. Read the displayed values before saving.

Schema types, identity and social profiles

Enable only the types you can populate correctly. Product, Organization, WebSite, breadcrumb, category and CMS type defaults are enabled in the shared definitions. FAQ defaults off; Blog defaults on but needs its contributor. Organization/WebSite can be requested on eligible pages. The visible breadcrumb trail owns the effective breadcrumb schema policy.

Org type defaults to Organization. Org name, legal name, description, URL, logo, email, phone, address, founding date and social-profile URLs have empty base values. Fill your real identity. Org aggregate rating defaults off. Do not supply a rating without the matching review data.

Products

Product brand source defaults to manufacturer. SKU source defaults to sku; MPN source defaults to mpn. Product condition defaults to https://schema.org/NewCondition. Product reviews enabled defaults on in the shared package, and output still needs a supported review source.

Publish selectable ProductGroup variants defaults on. Product variant mode defaults to productgroup. The alternative publishes a parent Product with a proven selected-item Offer, not an automatic price range. Review the attribute-to-schema-property matrix and any series-feature mapping before publishing variant data. The suite profile's variant limit is 50; the base shared definition uses 0.

Product dimension unit defaults to CMT. Price tax display defaults to auto. Price valid days has an empty shared default. Review actual images, selected variant, brand, identifiers, stock availability, tax display and price in the rendered JSON-LD.

Shipping and returns

Shipping data needs a real destination, carrier and delivery commitment. The base package enables shipping, but SEO Revolution starts with shipping off. Handling/transit minimum and maximum values are empty. Leave them blank until you enter actual commitments. Configure Shipping Currency only when the suite needs an explicit shipping-cost denomination.

Returns enabled defaults off. Returns days, return type, fees, method, refund type and physical return destination are empty in the shared base. Returns policy mode supports verified return terms or an Organization policy link. Link-only mode needs Organization placement and a published policy CMS page. Set country scope, placement, fees and exceptions according to the real policy, then preview a product before enabling output.

Additional types and cleanup

LocalBusiness and SoftwareApplication are optional contributors, initially off. The base software category is BusinessApplication and OS text is Web (PrestaShop). Identity/contact URL, accepted payments and currencies require your values. Contributor readiness determines whether those extra types can render.

Use the available preview, scan, dry-run and backup/restore tools before applying theme schema cleanup. Clean existing jsonld only replaces successfully prepared managed schema; ambiguous referenced conflicts can remain. Inspect the complete public page source to confirm the final combination of theme and module JSON-LD.

Image SEO

Open Content > Image SEO from the available content tools. Auto-generate alt texts defaults on. Alt text template falls back to %product_name%. The product generator supports:

%product_name% - %category% - %manufacturer% - image %position%

It also accepts %brand% and %reference%. The position placeholder counts from one when a position is available. Review missing-alt records, generate a small batch and check the image alt attributes in your theme. Filename metadata is stored separately; the module does not rename the image files themselves.

The Image SEO settings form has no WebP quality or lazy-loading controls. Legacy settings do not enable image conversion or lazy loading. Manage those operations with your image-processing tool.

Internal Links and Link Audit

Open Linking > Internal Links. Configure link groups, target URLs, language/shop targeting and the content rules you need. Initial limits are Maximum links per page = 5 and Maximum links per group = 3. Included HTML tags defaults to p,div,span,blockquote,li,td.

Prevent duplicate href, Prevent multiple autolinks in same element, Proportional global limit distribution, Even link distribution within text, Skip current page URL and Exclude headings default on. Prevent link in linked parent and Exclude bold/strong text default off. The default target is _self, rel is empty and CSS class is mpr-autolink. Debug profiling defaults off with an empty IP list. Turn it on only for a deliberate diagnostic check.

The former CSS included_selectors preference has been retired. The module applies links to supported saved content. Test a product, CMS and category content example instead of looking for the old selector field.

Use Linking > Link Audit to scan sources and check targets. The configured default budgets are 2000 sources, 50 targets and 168 hours of staleness. A standalone active mprinternallinking module can own live injection instead of suite groups. Read the ownership notice before adjusting the wrong set of rules.

Use Linking > Backlinks to import or manage backlink records and check sources. Default automatic checks are on, interval 7 days and batch limit 50. Use Disavow to manage/export the entries you intend to submit; saving a list is not the same as submitting it to an external service.

AI Generation

Open Tools > AI Generation and its settings. Set Primary Provider (openai initially) and the relevant OpenAI API Key, Anthropic API Key or Gemini API Key. The default models are gpt-4, claude-3-sonnet-20240229 and gemini-pro. Select a model that your configured provider accepts and test one draft.

Title generation prompt and Description generation prompt default empty. Max title length defaults to 60, Max description length to 160, and Writing style to professional. Review generated drafts before accepting or applying a bulk operation. Generation sends entity context to the chosen provider; this is separate from customer/order conversion tracking.

Indexing API

Open Indexing > Indexing API. Enable Google Indexing API and Enable Bing IndexNow default off. Configure the service account/key fields for the provider you use. Queue product updates defaults off for both providers.

Google's module-side daily quota defaults to 200, batch size 50 and verification delay 48 hours. Bing's quota defaults to 10000 and batch size 100. Queue retry defaults are 5 attempts, 30-minute base backoff and 21-day resubmission cooldown. Review the selected scope, tier map and service-category root before queuing broadly. A queued/submitted URL is not confirmation that a search engine has indexed it.

Search Console

Open Indexing > Search Console. Configure and complete the offered connection/authorization workflow, select the correct site property and run a small sync. Review query, page, country, device and URL-inspection results and the task messages. Credentials and permission to the selected property are required. A configured GA4 property is not a Search Console connection.

Open Technical SEO > LLMs.txt. Enable llms.txt and Also generate llms-full.txt default off. Language = Shop default initially. Categories, Products, CMS Pages and Blog Posts default included; Brands / Manufacturers defaults off.

Max products defaults to 50, Max blog posts to 30 and Product sort to Best sellers. Use Newest first, Name A-Z or Price high to low when appropriate. Exclude CMS IDs, Description, About and stored custom sections default empty. Exclude private or irrelevant pages before generating.

Save, generate and inspect the displayed file status and preview. Check /llms.txt and, when enabled, /llms-full.txt in the intended shop. The full file includes expanded content. Ensure the output location is writable and inspect any ownership/publication warning instead of overwriting an unrelated root file.

Open the Google Analytics area in Global Settings and review the tracking-ownership controls. Enter credentials and IDs only for the outputs you intend this module to own. Google/GA4 browser and server events require the relevant configuration and consent decisions; an enabled switch with blank IDs is not a working integration.

Credential/path defaults are empty unless shown otherwise.

For Google Tag Gateway, the Google tag ID is derived from configuration rather than a fixed string. Configure the measurement path, CF Zone ID and CF API Token before using Enable Tag Gateway. Use Disable Tag Gateway to undo that integration through the available action. Do not confuse the gateway controls with purchase-event credentials.

Test a paid test order and compare the browser event, queued server event and upload result. Check transaction IDs and tracking ownership to avoid duplicate events. Purchase uploads, retries and Customer Match are separate jobs with separate credentials and switches. Google Ads Validate Only can validate the configured upload request without treating that as a real submitted conversion.

Use the token shown by your shared MPR cron administration. The suite's root cron entry point supports:

* * * * * php /var/www/html/modules/mprseorevolution/cron.php --token=YOUR_TOKEN --max-tasks=20 --max-seconds=55 --context=cron

Replace the path and token. This runner processes shared MPR tasks, not only SEO tasks. Supported CLI arguments include --token, --max-tasks, --max-seconds, --context and --task for one module task. Review the registered schedule and returned result before adding more scheduler entries.

Jobs cover the configured sitemap, crawler, backlink, internal-link audit, Search Console, indexing and conversion queues. Tasks skip their work when their feature is disabled or SEO enforcement is inactive, so check each queue's own results to see what was sent.

Verify one product, category, CMS page, brand and supplier in each required language/shop. Inspect title, description, H1, canonical, robots, alternate links, Open Graph/Twitter output and JSON-LD. Test a redirect and a missing page. Check the sitemap index, child files, root robots file and any generated LLM files. Confirm visible internal links point to published pages. Use public uncached responses as well as your normal page cache.

If output is absent, check the module master switch, SEO Features, shop context, ownership, shared-package readiness, template integration and page cache. If files or jobs are skipped, read their status and enforcement state. If an external submission fails, inspect the relevant credentials, property/account selection and queue message. Re-run Tools > Integrity Check after fixing infrastructure problems.

Export or back up metadata, redirects, policies, SEO records, tracking queues, credentials configuration, generated files and root-file backups. Remove your scheduler entry if no other MPR module needs it.

The uninstall routine first restores owned route rules, then removes suite tasks, schema, menus and its unretained configuration. Shared sitemap tables remain when mprsitemapbuilder is installed; shared-package settings can also be retained for other owners. Do not assume uninstall restores every root file or deletes every generated artifact. Review robots.txt, sitemap/LLM files, theme patches and public URLs afterward, using the backups when you need restoration.

Verify native metadata and any replacement SEO/tracking owner before returning the shop to normal operation. Preserve the exported redirect data if old inbound links still need a destination.

Requires PrestaShop 1.6.0.0 or later and PHP 7.1 or later.