SEO Suite · Practical testing
Check SEO Changes on Your Storefront
A step-by-step way to tell whether an SEO Suite change really worked—without needing to be a developer.
A reliable five-minute check
1Change one itemUse a test product / language
2Save & reloadCheck the admin field stays saved
3Open storefrontUse the correct domain and language
4Inspect the resultVisible page, source or job log
Before blaming the extension
Check whether the setting is global, store-specific, language-specific, or admin-only. A saved admin change may not create an immediate visible storefront difference. Sometimes a cache, scheduled job, external search engine or theme determines what you see.
Visible storefront changeProduct heading, related products, working images or redirected address.
HTML/source changeMeta title/description, canonical, robots meta, JSON-LD, image attributes.
Admin/background resultAI queues, IndexNow jobs, diagnostics, sitemap/feed generation and logs.
How to inspect the page without coding
- View source. Open the public page, right-click → View Page Source. Use Ctrl+F to look for
<title>,description,canonical,robotsorapplication/ld+json. - Inspect rendered images. Right-click the actual product/gallery photo → Inspect and check its
altandtitle. The gallery may populate after page load. - Try another language. Change the storefront language and confirm text actually changes for translated fields.
- Try the correct store. On a multi-store OpenCart install, repeat using the right shop domain; canonical URLs, feed endpoints and SEO keywords may be store-specific.
- Use a private window. If you see old output, retry in a private window and check any OpenCart/theme/server cache.
Feature-by-feature verification checklist
| Feature | Where to check | Expected evidence |
|---|---|---|
| Meta Tags | Page source | Correct page title and description; search snippets may differ. |
| Quick Editor | Admin reload + storefront | Edited field remains saved and matches the right language/store. |
| AI Content / Templates | Settings reload + preview + page | Mode saves; generated text persists where expected. |
| Additional image Alt/Title | Product → Images + Inspect | Different gallery images/languages show their correct attributes. |
| SEO URL Manager | Browser address | Friendly public URL opens the correct page without errors. |
| Canonical | Page source | Appropriate rel="canonical" URL. |
| Indexing | Rule Tester + source | Expected robots meta only where applicable. |
| Structured Data | JSON-LD + validator | Valid facts that match visible product information. |
| XML Sitemap | Public sitemap URL | Readable valid XML with correct public URLs. |
| IndexNow | Admin queue / logs | Submission processed or useful error; not immediate search placement. |
| Robots.txt | /robots.txt | Public text contains intended crawler instructions. |
| Broken Link Manager | Old public URL | Relevant replacement, without a loop or another 404. |
| Disabled Redirects | Old disabled page URL | Correct redirect if replacement was intentionally set. |
| Product Tags | Admin tags + storefront search | Saved relevant tags; storefront search depends on configuration. |
| Related Products | Public product page | Relevant products shown if the theme displays them. |
| AI Product Feed | Export URL/file | Correct products and links, per store/language. |
| Image Organizer | Admin history + page | Renamed image still loads; Undo works where allowed. |
| WebP Optimizer | Network → Img | Correct modern image delivery where supported; no broken images. |
| SEO Health | Admin audit details | Issue status changes after the audit refresh. |
| Cron Manager | Admin last run/log | Enabled jobs execute after the scheduler is configured. |
What search engines can and cannot confirm
You can immediately verify your page and source code. Search Console and other search engines may take time to crawl and process it. No feature guarantees a ranking, an indexed page, a rich result or a shopping listing.
If the change does not appear: save again, check the language/store, inspect the source of the right page, confirm any required background job ran, and clear only relevant caches. For a third-party theme, inspect the actual rendered DOM before declaring the feature broken.