On-page SEO
Review title, description, headings, word count, visible content and selected document metadata.
SEO Browser Extension
Open the browser companion on any permitted page to review on-page SEO, indexability, links, images, structured data and social metadata, then save selected findings to Nuvyqo.
Planned initial module. Store installation links will appear only after development, privacy review, browser testing and marketplace approval.
Demonstration analysis of the page opened when the user invoked the extension.
Eight active-page capabilities
The first purpose is narrow and clear: inspect the active page the user chooses, explain what is visible and route selected findings into the Nuvyqo workspace.
Review title, description, headings, word count, visible content and selected document metadata.
Inspect canonical, robots directives, hreflang, response context and sitemap or robots references.
Classify internal, external, followed, nofollowed, sponsored and UGC links and check selected statuses.
List images, alt text, titles, dimensions, loading attributes and visible accessibility gaps.
Display JSON-LD and selected schema types without claiming eligibility or rich-result approval.
Review Open Graph, X card fields, share titles, descriptions, images and canonical consistency.
Compare selected raw and rendered fields where browser access allows JavaScript differences to be observed.
Send the current URL and user-selected findings to Page Analyzer, projects, tasks or reports after login.
Privacy-first permission model
The planned extension uses the narrowest practical permissions and avoids persistent access to every page merely to support future features.
How it works
Navigate to the public or authorised webpage you need to review.
Click the browser action so temporary access is granted for the current tab.
Inspect page-level SEO, links, images, schema and visible limitations.
Save selected findings, open Page Analyzer, create a task or generate a report.
Practical use cases
Check titles, headings, canonical tags, social fields, images and structured data before launch.
Inspect visible page structure and links without claiming access to private analytics.
Review heading order, image descriptions, page metadata and connected source pages.
Save selected page findings and the current URL to an authorised Nuvyqo project.
Active URL → observed element → source → action
Observed facts before recommendations
The extension should explain which checks came directly from the active page, which require a network request and which depend on account-based provider data.
Browser companion and web application
| Task | Browser Extension | Nuvyqo Web Application |
|---|---|---|
| Page scope | The current page selected by the user. | Saved projects, multiple URLs, crawls and historical results. |
| Immediate checks | Document metadata, headings, links, images, schema and social fields. | Deeper analysis, prioritisation, account rules and cross-page evidence. |
| Provider metrics | Displayed only after user request and account entitlement. | Usage-controlled rankings, keywords, backlinks, monitoring and reports. |
| Data persistence | Local preferences and user-selected saves. | Authorised project history, reports, tasks and scheduled workflows. |
| Best use | Fast inspection during normal browsing. | Ongoing website management, analysis and collaboration. |
Clear limitations
Browser-internal pages, store pages, protected contexts and some embedded frames may block extension access.
The extension cannot replace full project crawling, monitoring or historical analysis.
Performance, rankings, backlinks and keyword data may require remote services, quotas and account limits.
Final capabilities, permissions and browser availability remain subject to development and marketplace review.
Related modules
Browser Extension FAQ
The planned extension analyses the page the user actively opens and requests. It can review titles, descriptions, headings, canonical and robots directives, structured data, images, outgoing links, social metadata and selected technical signals.
No. The planned privacy-first design uses a user-invoked analysis model. It should inspect the active page only after the user clicks the extension or performs another clear action.
The first release is designed around the narrowest practical permissions, such as activeTab, scripting and storage. Any additional host or account permission should be optional, explained and requested only when a related feature is used.
Basic page analysis can be performed locally where practical. Account-based metrics, saved projects or cloud reports may require selected page data or URLs to be transmitted securely after disclosure and consent. The final privacy policy will list exactly what is processed and retained.
It may inspect visible page elements when the browser permits access and the user invokes the extension, but it must not bypass authentication, paywalls or restricted browser pages. Sensitive content should not be saved without explicit user action.
The planned workflow supports comparing selected SEO fields from the original document and the rendered page where browser access allows it. This can help identify JavaScript-generated changes.
The extension can show lightweight local observations and provide a handoff to Page Analyzer or approved performance services. Full laboratory or field-performance data may require external APIs, quotas and account limits.
The product direction supports saving the current URL, selected findings and notes to an authorised project after login. Nothing should be saved to the account until the user chooses that action.
The product direction targets Chromium-based browsers first and keeps the code architecture compatible with WebExtension standards where practical. Firefox release timing will depend on testing, permissions and store review.
Not yet. This public page describes the planned browser companion. Store links will be added only after the extension is built, reviewed and approved.
Browser companion roadmap
Create an account and add the website project. Store links will be published only after the browser extension is tested, reviewed and approved.