SEOquake implementation handoff

Historical implementation request. The verification above is the current status.

Medium priority · Approved copy and mockups · Revises the chrome-4 trial implementation

Completed: The Quick View trial destination and popup_free_trial / empty_cta tracking work in the reviewed package. The changes below update the wording and correct the Full Report scope leak.

Issue: “Try it on semrush.com” suggests a demo, but opens the homepage or dashboard without explaining what to do next. The trial line also calls connected users “new” and appears in Full Report’s unsupported-page screen.

Approved copy:

• Button, both states: Open semrush.com
• Disconnected: New to Semrush? Start a 7-day free trial
• Connected: Using a free account? Start a 7-day free trial

Fix:

• In src/components/shared/PageAnalysisState.tsx, use useSurfaceContext from src/context/SurfaceContext.tsx to scope the new button label and secondary copy to variant === 'unsupported' && surface === 'popup'. Remove the secondary trial line from Full Report; retain its existing message and primary Action.
• Use the existing useSemrushConnection().connected state for the two trial-line introductions. Connection does not establish a paid plan or website login. Keep the heading, explanation, primary button position and existing line styling.
• Change only the Quick View primary label to Open semrush.com. Keep its existing https://www.semrush.com destination and other / empty / empty tracking inputs: popup_other / empty_empty.
• Keep the trial link’s shared Link and free_trial / cta / empty tracking inputs in src/utils/semrush/utm.ts. Both states use the same tagged destination below. Preserve the connection card’s free-account signup link and the separate Full Report Semrush trial banner.

Tagged trial destination: https://www.semrush.com/semrush-free-trial/?utm_source=seoquake&utm_medium=toolbar&utm_campaign=popup_free_trial&utm_content=empty_cta&ref=174537735

Scope: Copy and placement only. Keep SEObar excluded from Semrush, including its homepage. No new exposure tracking or automatic rollout/revert threshold.

Earlier specification · superseded copy and scope

Historical reference only. The approved copy and Fix above supersede the original button label and connection-state wording.

Medium priority · Approved copy and mockup · Implementation not yet verified

Issue: Quick View’s unsupported-page screen offers a general Semrush button but no direct trial link. Add a secondary route without changing the existing button or its attribution.

Approved copy: New to Semrush? Start a 7-day free trial

Fix:

• In src/components/shared/PageAnalysisState.tsx, add the line below Action only for Quick View’s unsupported variant. Use the existing surface context to keep it out of Full Report and other states. Reuse the typography, link treatment and spacing of Quick View’s “New to Semrush? Create a free account” line; keep the approved mockup’s placement and the primary button’s position.
• Use the shared Link component for “Start a 7-day free trial”, with href="https://www.semrush.com/semrush-free-trial/" and destination: 'free_trial', placement: 'cta', panel: 'empty'. With the popup tracking surface, withSemrushTrackingParams generates popup_free_trial / empty_cta. Do not add a qualifier or connection-state suffix.
• Add 'free_trial' to SemrushDestination in src/utils/semrush/utm.ts if still absent in the current branch. Reuse the existing builder and its source, medium and referral values; confirm the resulting URL against the tagged link below.
• Leave “Try it on semrush.com” unchanged: label, position, destination and destination: 'other', placement: 'empty', panel: 'empty'. Its existing popup_other campaign and empty_empty content stay separate from the new trial link. Keep the free-account signup link on the Semrush connection card unchanged.

Tagged destination: https://www.semrush.com/semrush-free-trial/?utm_source=seoquake&utm_medium=toolbar&utm_campaign=popup_free_trial&utm_content=empty_cta&ref=174537735

Scope: One secondary link in Quick View’s unsupported-page state, such as a new tab, browser settings or the Web Store. Retain that state’s existing connected/disconnected availability; no new account-status targeting, automatic navigation, permission or telemetry request. This is an outbound trial landing-page link, not OAuth or account signup.

Code references were checked in the local checkout; confirm the equivalents in the implementation branch. The separate campaign preserves attribution separation, not a guarantee of unchanged registration volume.

Engineering checks

• Open Quick View on a new tab, browser settings and the Chrome Web Store. Confirm the exact copy and fully visible line below the unchanged primary button at the normal popup size. Check connected and disconnected states.
• Click the new link and verify a new tab opens the exact trial URL with utm_source=seoquake, utm_medium=toolbar, utm_campaign=popup_free_trial, utm_content=empty_cta and ref=174537735. Preserve keyboard focus and activation.
• Click the original button and compare its destination/tags with the previous package: popup_other / empty_empty remains unchanged. Confirm the new campaign can be distinguished in the reporting readout; a click does not establish a trial or registration.
• Confirm no new trial line appears in paused, reload or migration-error states, ordinary report content or Full Report. Preserve the existing free-account connection-card copy/link.

Historical implementation request. The verification above is the current status.

Low priority · Pending in 4.3.3-chrome-4 · Approved copy

Issue: “Analyze this page in Semrush” repeats context already provided by the link row. Shorten it to match the other action tooltips.

Approved copy: Analyze in Semrush

Fix:

• In the shared Semrush Links row action, change the tooltip’s content and the anchor’s aria-label from Analyze this page in Semrush to Analyze in Semrush. Apply to Quick View → Links and Full Report → Links.
• Keep aria-describedby, anchorRef and compactMode behavior intact. Preserve the icon, row-specific destination, tracking, hover/focus and Escape dismissal.

Both old strings remain in 4.3.3-chrome-4/chunks/semrush-B_AqKuds.js. Update the source component that generates this action; do not patch the compiled bundle. The local proposal and 4.3.3 Design tab already use the new wording.

Historical implementation request. The verification above is the current status.

Medium priority · Matching flaw confirmed in chrome-4 · Targeted correction

Issue: Built-in URL patterns can hide SEObar on unrelated sites: the Bing rule matches climbing.com and benjaminfranklinplumbing.com, while the Semrush rule matches example.com/?next=semrush.com/. These are unintended exclusions, even when the user has enabled the bar.

Fix:

• In src/utils/seobar/urlFilters.ts, review all 16 DEFAULT_EXCLUDES rules and their use through DEFAULT_EXCLUDE_EXPRESSIONS in isSeobarAllowedOnUrl. Match the intended hostname and supported subdomains with explicit boundaries; domain mentions in a path, query or user info must not qualify.
• Prefer parsed URL.hostname for host checks, with explicit path/query predicates where the original rule requires them. Preserve intended host coverage and restrictions such as search paths; do not turn path-specific exclusions into blanket domain blocks.
• Keep Semrush excluded, including the homepage, app and checkout. Preserve user-entered settings.matches and settings.excludes regex behavior, HTTPS settings and existing enable/pause controls. This ticket changes built-in rules, not saved user rules.

Confirmed by evaluating the packaged rule patterns, not by a new live-browser test. This is separate from the completed “For this domain” rule fix. If the full correction cannot be verified in time for 4.3.3, carry it into the next patch rather than ship a partial rule rewrite.

Medium priority · Not included in 4.3.3-chrome-3 · Required before this release’s submission

Captured layout: The saved HTML/CSS defines a 64px fixed rail and a separate 261px navigation panel with open/close controls. These dimensions describe this capture only; measure the visible bounds at runtime instead of hard-coding either width.

Issue: Google sometimes places navigation in the left rail occupied by SEOquake’s sidebar. Our collapsed logo or expanded controls can cover Google’s controls.

Fix:

• Extend the host positioning in syncSerpControlPanel / applyPanelPosition in src/utils/serp/syncControlPanel.ts. Measure the visible Google rail and available space before the results. Keep the familiar left placement when it fits; offset past the rail with a small gap when needed. Check the expanded panel and its flyouts, not just the collapsed logo. In this capture, aim-lhs-panel-container, role="navigation" and the Open sidebar / Close sidebar controls provide inspection clues. Validate visibility and geometry; do not rely solely on generated class names or English labels.
• If the expanded controls will not fit, render a compact SEOquake button immediately above the first organic result on the current page. Reuse the organic classification around detectOrganicResults in google/base/detect.ts, but do not wait for a redirect destination or metric strip to resolve before locating that result. Exclude ads; do not anchor to the AI Overview or its separate Analyze sources control.
• Reuse SerpControlPanel.tsx controls in a dismissible panel opened by the compact button. Keep Parameters, Export CSV, Keyword data, Locale and enable controls available. Fit the panel within the viewport, preserve theme and keyboard focus, and support Escape/outside dismissal with focus returned appropriately.
• Keep layout mode separate from the saved settings.panelCollapsed preference and patchSerpSettings. Temporary collision handling must not overwrite the user’s choice. Reuse one panel host; do not create duplicate controls or change sides as the user scrolls.
• Recompute placement on window resize and relevant Google rail/result-layout changes. Integrate with the batched lifecycle around watchSerpMutations in google/base/observe.ts; ignore our own changes and remove added listeners/observers through unmountSerpControlPanel. Avoid constant polling or full-page scans on scroll.

Scope: Positioning and access to the existing controls only. Preserve metric strips, numbering, Analyze sources, saved settings and tracking. No added permissions or automatic switch to a right-hand sidebar. If no organic result is available yet, do not attach the fallback to an ad or AI module; wait for an eligible anchor without obstructing Google.

Local debugging evidence: /Users/babepig/Downloads/seo checker - Google Search.html and its seo checker - Google Search_files/ folder. Keep the raw saved page and assets local; they may contain page/session metadata and are not bundled with this handoff.

References were checked in the local source checkout; confirm their current equivalents in the implementation branch. The older sidebar design remains the control-style reference; this ticket supersedes its fixed-left placement rule. Engineering may choose another layout implementation that meets these outcomes.

Medium priority · Approved copy and destination · Implementation not yet verified

Issue: Full Report’s connected Semrush panel currently promotes MCP. Replace that banner’s copy and link with the approved free-trial offer, while retaining MCP in Quick View’s connected tips.

Approved copy:

• Headline: See What’s Behind These Numbers
• Body: Get AI visibility, keyword, backlink, and competitor data for any site, all in Semrush One.
• Button: Try Free for 7 Days

Fix:

• In src/components/report/panels/SemrushPanel.tsx, update only the connected branch’s MCP Cta title, text and link. Reuse src/components/shared/Cta.tsx unchanged so the banner keeps its existing position, styling and responsive behavior. Leave the disconnected branch unchanged.
• Set the button destination to https://www.semrush.com/semrush-free-trial/. Pass destination: 'free_trial', placement: 'cta', panel: 'semrush' and connectionState: 'connected' through the shared Link tracking. With the report surface, withSemrushTrackingParams must produce report_free_trial / semrush_connected_cta; do not use the popup campaign.
• Reuse the 'free_trial' addition to SemrushDestination in src/utils/semrush/utm.ts from the Quick View trial-link ticket. Add it once if absent; preserve the builder’s source, medium and referral values.
• Keep the connected semrush tip in src/utils/popup-tips/messages.ts unchanged: “Explore Semrush MCP”, its MCP destination, eligibility, rotation and tracking. Do not remove 'mcp' from the tracking types or change other banner/tip placements.

Tagged destination: https://www.semrush.com/semrush-free-trial/?utm_source=seoquake&utm_medium=toolbar&utm_campaign=report_free_trial&utm_content=semrush_connected_cta&ref=174537735

Scope: Full Report → Semrush, connected users only. Copy and outbound link replacement; no new banner, OAuth flow, account-plan targeting or permissions. Preserve the existing new-tab behavior. Trial eligibility remains determined by Semrush’s landing page.

Code references were checked in the local checkout; confirm their equivalents in the implementation branch. The Semrush One wording above is approved for this banner; it does not change the separate free-account connection copy.

Low priority · Approved copy · Implementation not yet verified

Issue: SERP metric tooltips repeat the metric name in a bold heading above the description. The extra line makes them larger and covers more of the search results.

Fix:

• Update SERP_PARAMETER_TOOLTIPS in src/utils/parameters/meta.ts with the approved descriptions below. In src/components/shared/parameters/ParameterByKey.tsx, stop passing serpTooltip.title as the visible tooltipTitle for the SERP variant. Retain the metric’s full name for accessible identification.
• In src/components/serp/overlay/SerpConnectedMetrics.tsx, update the five connected-metric descriptions and omit the visible title from InfoTooltipBubble. Keep one description with the existing body typography and content-sized height; do not leave an empty heading or its spacing.
• Apply the same copy through the shared organic-result and expanded Analyze sources metric components. Keep existing tooltip availability in AiSources.tsx; do not enable tooltips on compact source cards where they are currently disabled.
• Preserve light/dark appearance, placement, hover delay, keyboard focus, Escape dismissal and accessible descriptions. Keep the existing “Couldn’t load. Click to retry.” error override and retry action unchanged. Scope this to SERP metric tooltips; do not remove headings globally from the shared tooltip component or alter Quick View, Full Report, SEObar or sidebar-control tooltips.

Approved copy: The first column identifies the current heading; remove it from the visible tooltip. Show only the new description. Current strings were matched in 4.3.3-chrome-3.

Code references were checked in the local checkout; confirm the current implementation-branch equivalents. Keep metric definitions, values, destinations and tracking unchanged.

Medium priority · Approved copy and mockup · Connected and disconnected users

Issue: Quick View’s Audit tab ends after the page checks, often leaving unused space. Add a clear next step for users who want to audit the whole site.

Approved copy:

• Headline: You Checked One Page. Now Audit the Whole Site.
• Body: Scan your site for 140+ SEO and AI search issues, and see what to fix first.
• Button: Try Free for 7 Days

Fix:

• In src/components/popup/panels/AuditPanel.tsx, place the banner after the passed section, outside its Collapsible, in the existing scroll flow. When there are no passed checks, keep it below the remaining audit content. Do not pin it above the tip bar or limit eligibility to pages with few issues; expanding passed checks moves the banner below that content.
• Reuse the purple treatment from src/components/shared/Cta.tsx, adapting the content/button stack to the popup mockup without changing existing Full Report banners. Reuse close.svg and the close-control treatment from shared/layout/TipBar.tsx in the top-right corner, with an accessible label such as “Dismiss site audit offer” and room for the headline to wrap.
• Gate visibility on settings.general.showTips from useAppSettings and a separate persisted banner dismissal. Wait for settings and dismissal storage to load before showing it, so a dismissed banner does not flash. Apply the same rule to connected and disconnected users; do not infer paid-plan or trial eligibility from connection status.
• Follow the #imports storage pattern in src/utils/popup-tips/storage.ts, but use a dedicated banner key, for example local:popup.auditTrialDismissedAt. On X, hide immediately and persist the dismissal time for 7 * 24 * 60 * 60 * 1000 milliseconds. The dismissal applies across pages and popup reopenings in that browser profile. After expiry, show it on the next eligible Audit view; no background polling is needed. Clean up any storage subscriptions and handle write failures without treating an unsaved dismissal as persisted.
• Keep the banner key independent of local:popup.tipDismissals, dismissPopupTip and tip rotation. Closing the banner must not dismiss the tip bar; closing the tip bar must not dismiss this banner. Turning Show tips off hides both, but does not erase or restart the banner’s seven-day clock.
• Use the shared Link with href="https://www.semrush.com/lp/website-audit-1/" and destination: 'site_audit', placement: 'cta', panel: 'audit'. The popup surface produces popup_site_audit / audit_cta through withSemrushTrackingParams in src/utils/semrush/utm.ts. Omit connection-state suffixes and qualifiers; site_audit already exists in the destination type.
• Remove only the Audit tip with ctaText: 'Open Site Audit' from src/utils/popup-tips/messages.ts. Keep the other Audit tips, including the internal “View audit report” action, and leave Full Report Site Audit CTAs unchanged. Verify rotation still handles the reduced list. The old tip used audit_tip, while this banner uses audit_cta; removing it prevents future campaign-level mixing, but historical popup_site_audit totals still include prior tip traffic.

Tagged destination: https://www.semrush.com/lp/website-audit-1/?utm_source=seoquake&utm_medium=toolbar&utm_campaign=popup_site_audit&utm_content=audit_cta&ref=174537735

Scope: One banner in Quick View → Audit only, not other tabs, Full Report or unsupported-page states. Reuse existing storage permissions and outbound new-tab behavior. Clicking the CTA does not start the dismissal clock; X does. Trial eligibility remains with Semrush’s landing page.

Code references were checked in the local checkout; confirm current implementation-branch equivalents. Copy and destination are user-approved; the offer’s live eligibility and “140+” claim were not independently verified in this handoff edit.

Unresolved observation: Beatus saw metric strips disappear together and reappear seconds later in 4.3.2-chrome-3. The cause is not established. Preserve this for targeted reproduction; the redirect fix and later smoke pass do not prove it resolved. Progressive loading alone is a separate behavior.

Historical November 4 review below. The closeout above supersedes its former open status; original evidence and mockups are preserved.

Medium–high priority · Partially implemented · Live review November 4 · 4.3.2-chrome-2

Completed: Position numbers render independently of destination lookup. All eight organic results were numbered in live review. Bounded retries are running; controlled checks also passed delayed recovery, changed links and navigation.

Issue: Five of eight organic results still had no metric strip. Refreshing changed which results displayed metrics but did not clear the issue. The background capture recorded five Google /goto URLs returning HTTP 200 on all three attempts. The inspected response was HTML without a Location header; the resolver accepts only validated redirect destinations and discards the response body.

Investigation and fix direction:

Engineering discretion: Use these points as a starting point. Investigate other causes or approaches if the evidence supports them. The required outcome is reliable metric strips for the correct result URLs, while preserving working position numbers, security safeguards and performance.

• In redirectsBackground.ts, capture and inspect a failing HTTP 200 response before it is discarded. Establish whether it provides a valid exact destination or whether the result contains another reliable source for that URL.
• Recover and validate the exact destination before loading its metric strip. The implementation approach remains unverified; do not assume every HTML response contains a usable URL or prescribe a parser before inspecting it.
• Preserve the independent numbering and bounded retry/backoff behavior in resolveOpaqueGoogleRedirect. More retries alone will not resolve the repeated HTTP 200 case.
• Keep the result-identity and href-change handling in detectResults/syncOverlays. Retain known-good metrics only for the same result; never attach another page’s metrics.
• Retain credential omission, manual redirect handling and batched observation. Do not visit every result automatically or guess exact destinations from abbreviated display URLs.

Still to establish: The HTML body was unavailable in DevTools because the resolver cancels or aborts it. We have confirmed the response mismatch, but not whether the body contains a destination, an interstitial or another response. Verify the chosen correction on real Incognito results before closing this ticket.

Files: src/utils/serp/google/redirectsClient.ts, redirectsBackground.ts, google/base/detect.ts, google/base/observe.ts, google/base/positionNumber.ts and src/utils/serp/syncOverlays.ts. Confirm the current source equivalents; change source, not generated bundles.

Live evidence · November 4 · 4.3.2-chrome-2

All eight positions appeared. Metric strips were present for Backlinko, Yoast and Chrome Web Store, and missing for Seobility, SEOptimer, Semrush, Rank Math and DebugBear. After one refresh, a changed result set still had five missing strips. The network capture included 15 HTTP 200 responses across five lookup URLs, with three attempts per URL.

The initial page was inspected before opening worker DevTools. The refreshed load was captured with DevTools open, which keeps the worker awake. No product code or settings were changed.

Original diagnosis and user screenshots · November 3

In 4.3.0 and 4.3.1, a failed destination lookup was cached without expiry or automatic retry, hiding both the number and metrics. Controlled tests confirmed that flaw. The 4.3.2 candidate corrects numbering and retry behavior; the remaining live response case is described above.

The first capture shows positions 5, 8 and 9; the later capture shows 1, 4, 7 and 8. Numbers and entire metric strips change together. These are full-page references; sponsored results are expected to remain unnumbered.

Historical November 4 review below. The closeout above supersedes its former open status; original evidence and mockups are preserved.

Medium priority · Reviewed package: 4.3.3-chrome · Package checks and Beatus’s live review, November 4

Completed: The Links tab, occurrence-level filtering, background checks after popup closure, highlight persistence and filtered CSV download passed focused package checks. Preserve these behaviors and the existing Semrush destinations, tracking and permissions.

Design reference: 4.3.3 Links redesign and Technical specs. Track the remaining revisions here; keep the approved mockups intact.

1. Keep action tooltips clear of neighboring buttons

Issue: Download and highlight tooltips can cover neighboring action buttons and intercept clicks. Users must dismiss the tooltip before they can use the covered control.

Fix:

• Adjust the Links action buttons’ InfoTooltipBubble placement and data-tooltip-boundary handling so tooltips stay clear of adjacent controls. Changing pointer-events alone is not enough: neighboring buttons must remain visible and clickable.
• Review interactive and pointer-event handling for these informational tooltips. Cover Find broken links, Show these links on the page / Clear highlights, and Download this list as CSV / Downloaded; preserve focus and Escape dismissal.

2. Open the matching Full Report Links section

Issue: View Full Report opens Page Info while Quick View’s Links tab is active, losing the user’s report context.

Fix:

• Update getReportTargetFromPopupTab in src/utils/surface/navigation.ts to map the Links tab to the Links report.
• Pass the selected Internal/External kind through Header/NavButton to openReportFromPopup. Keep the source tab and existing report-dropdown routes intact.

3. Add Clear filters to the empty state

Issue: An unmatched search leaves users with an empty list and no single action to reset the search and filters.

Fix:

• In the Links empty-state renderer, use No links match these filters. and add Clear filters, matching the mockup.
• Reset query to empty and follow/status to all. Preserve kind and statusByUrl so the selected section and completed checks remain intact.

4. Gray out zero-count filter options

Issue: Zero-count filter options look available and can be selected, leading to an empty list.

Fix:

• Use each option’s existing count to apply disabled and the approved muted styling in the Follow and Status menus. Keep all available as a reset option.
• Update the menu’s Arrow/Home/End focus handling to skip disabled options. Recalculate availability when the scope, search or other filters change.

5. Show additional anchor variants

Issue: Grouped URLs show one anchor and an occurrence count, but give no indication that other occurrences use different anchor text.

Fix:

• Derive distinct variants from each filtered row’s occurrences, using anchorType plus whitespace-normalized anchorText. Render +N more for the variants beyond the displayed anchor.
• Use the collector’s existing image-alt text; do not invent labels for SVGs or empty anchors. Repeated empty anchors of the same type count as one variant; empty text, IMG and SVG variants remain distinct because their displayed badges differ.
• Keep buildLinkRows URL grouping and occurrenceCount unchanged. Repeated identical anchors must not increase the variant count; preserve occurrence-level filtering and Mixed handling.

6. Include the selection in the highlight chip

Issue: The highlight chip shows only a count, so users cannot see which scope and follow filter remain active after Quick View closes.

Fix:

• Build the content-script chip text from the active links:page:highlight filters: kind and follow. For example: 19 external dofollow links highlighted; omit the follow qualifier for all.
• Keep the existing highlighted-occurrence count, Clear action, popup-close persistence and navigation cleanup.

References checked against the 4.3.3 package and existing shared source. Apply changes in the corresponding source components, not generated bundles.

The separate missing Google metric-strip issue remains on the existing 4.3.2 SERP recovery card. It is not duplicated here.

Issue: Quick View and Full Report stay light, but their shared tooltip styles respond to the system’s dark preference. Tooltips can therefore use a dark background on the white report. SEObar and SERP Overlay already follow their own selected appearance.

Fix:

• Resolve the shared Tooltip appearance from its owning surface. Keep Quick View and Full Report tooltips light under both system preferences, including tooltips rendered through a portal.
• Reuse the existing light treatment: white background, dark heading/body text, light border and current shadow. Apply the same appearance to the arrow. Keep the approved copy, sizing, spacing and placement.
• Preserve SEObar’s selected Light/Dark appearance and SERP Overlay’s Light/Dark/Match Google behavior. Avoid changing the global dark: selector or removing dark support from shared tooltips.
• Keep hover, keyboard focus, Escape dismissal, accessible associations, interactive links and the current delegated tooltip lifecycle unchanged. This is a theme correction, not another tooltip implementation.

Scope: Quick View and Full Report tooltip appearance only. No report dark-mode feature, new preference or changes to metric-error styling.

Files: Shared tooltip renderer and the app’s surface/theme wiring. src/components/shared/Tooltip.tsx is the local source reference; confirm its current source equivalent. In the reviewed package, chunks/download-Bb8NZV5h.js contains renderer Ro and assets/download-D9G6iL8w.css applies tooltip dark: styles through prefers-color-scheme. Change source, not generated bundles.

Earlier appearance · October 28 references

Measured result: Across 30 controlled article tabs, Chrome 3 SEObar used 1,845.5 MiB of aggregate browser-process footprint versus 1,887.5 MiB for Chrome 3: a 42 MiB reduction. Paired savings were 38 and 46 MiB. Tab JavaScript heap fell from 73.03 to 65.91 MiB, about 9.75%, and median listeners fell from 245 to 190 per tab. The 10-tab comparison also improved.

• Retain the now-passed tooltip interaction checks as regression coverage: hover, keyboard focus, placement and Escape after layout changes.
• Preserve the verified performance change, metrics, preferences, connection state, layouts and existing-tab controls alongside the completed hotkey correction.
• For any later memory change, repeat matched enabled/off comparisons and inspect retained-object ownership. Do not use feature removal as evidence of an optimization.

Status: Completed. These checks are a reference for future changes, not outstanding work on this card.

Working as tested: All three sequences made four API requests on the first visit and zero on the immediate repeat. The three cached metric entries survived natural worker termination with their original fetch timestamps. The post-restart request count was not captured. This is a regression check, not another defect or a replacement for the audit-header cache fix.

• Keep cold and repeat visits separate. With the same selected parameters and fresh session cache, verify that repeat visits reuse valid entries instead of restarting every metric request.
• Allow the worker to stop naturally without DevTools keeping it alive. Revisit the page and confirm that valid entries survive without stale URL/account data. Check expiry and account-change behavior, including connected metrics.
• Retest saved preferences, Semrush connection and metric/CSV completeness after each performance change. Compare the final candidate with the unchanged baseline.

Historical specification. The verified closeout above supersedes its open status.

High priority · Confirmed in 4.3.0, Chrome 3 and Chrome 3 SEObar

Issue: With SEObar’s “Minimize to icon” setting enabled, typing S inside some embedded editors toggles the bar instead of entering the letter. useSeobarMinimize checks only event.target. For fields inside shadow DOM, that target is the outer component rather than the editable field, so the handler calls preventDefault() while the user is typing.

Fix:

• Update isEditableTarget and the handleKeyDown guard to consider event.composedPath() and the active editing context, including editable ancestors and supported textbox/editor controls. Skip the shortcut whenever focus is in a text-entry control.
• Handle closed shadow components conservatively. Their internal fields are not exposed in the event path, so composedPath() alone is insufficient. When the editing state cannot be established, allow the key through rather than suppressing the typed character.
• Ignore composition and already-handled events, and review repeated keydown events and physical KeyS matching so other keyboard layouts do not lose text. Preserve existing modifier exclusions and click-to-expand behavior.

Scope: The existing SEObar shortcut handler in horizontal and vertical layouts. Protect typing without requiring users to discover a setting or workaround. Do not redesign SEObar or add a new shortcut preference as part of this fix.

Files: src/hooks/useSeobarMinimize.ts, including isEditableTarget, handleKeyDown and its document capture listener. Source path is a reference; matching logic was independently verified in both supplied Chrome 3 packages.

Historical specification. The verified closeout above supersedes its open status.

Medium priority · Confirmed in Chrome 3 SEObar · Inherited from legacy 3.13.5

Issue: “For this domain” builds an exclusion by appending window.location.host to ^http(s)?://. The hostname’s dots are treated as regex wildcards, and the pattern has no host boundary. Excluding example.org therefore also hides SEObar on unrelated hosts such as examplexorg and example.org.other.test.

Working behavior: The exclusion saves and remains effective on the selected host through navigation, reload, a new tab and browser restart. This is a matching correction, not a fix for lost settings. Legacy 3.13.5 generated and evaluated the same pattern.

Fix:

• Make buildDomainExcludePattern treat the selected host as literal text and enforce the end of the host. Escape regex metacharacters and use a proper boundary, or use an equivalent structured host comparison. Retain HTTP/HTTPS handling and the current explicit-port behavior.
• Preserve the current host scope. Excluding example.org must not silently expand to www.example.org or other subdomains. Site-wide exclusions and changes to the control’s wording are separate product decisions.
• Keep manually entered regex rules working through isSeobarAllowedOnUrl. Review how previously generated exclusions can be corrected safely; do not rewrite stored entries whose origin or intent cannot be established. Keep appendSeobarExcludePattern deduplication and existing settings persistence intact.

Existing rules: The current list stores generated and manual expressions together without a provenance marker. Robert should identify a safe treatment for old generated entries and state any remaining limitation. A matching-looking string alone is not proof that it was generated automatically.

Scope: SEObar’s “For this domain” action and its generated host-exclusion rules. No change to the Google SERP overlay, global pause, whitelist behavior, custom regex semantics or default visibility.

Files: src/utils/seobar/urlFilters.ts (buildDomainExcludePattern, appendSeobarExcludePattern, isSeobarAllowedOnUrl); src/components/seobar/layout/SeobarCloseDropdown.tsx. Confirm the source equivalents in the current implementation before editing; supplied-package matching logic was independently verified.

Historical specification. The verified closeout above supersedes its open status.

UX-01 · Low priority · Styling correction only

Completed: Pinterest failures now show an error and remain eligible for Retry and Request all parameters. HTTP 429/500 and transport-failure recovery passed in both Chrome 3 packages. Genuine zero stays numeric; a successful empty response stays n/a. Previously completed Backlinks, domain and AI-source retry work remains complete.

Issue: With a dark system color preference, the white Full Report displays “Couldn’t load” in white. The shared error label uses text-gray-darker dark:text-white, so the system preference changes the text without changing the report surface. Retry remains visible and works. This is a presentation issue, not a recurrence of the Pinterest recovery bug.

Fix:

• In the shared metric-error component used by the Links table, remove the OS-triggered dark:text-white from the light report label and dark:text-lavender from its Retry control. Keep text-gray-darker and text-blue so both remain readable on the white report under either system preference.
• Scope the change to the light app/report error treatment. If the source component also serves a genuinely dark surface, use an explicit surface variant. Preserve the separate serp-ui.js error renderer and overlay theme styles; do not change the global dark-mode selector.
• Keep role="status", Retry’s accessible name, keyboard focus and onRetry unchanged. Preserve the working Pinterest service/message handling, manual and bulk retry, and zero/empty formatting. No request or retry orchestration changes are needed.

Fix validation: Removing only those two classes in a temporary browser DOM override kept the label dark under both system preferences. Retry remained readable and recovered a real zero. This validates the color correction; the rebuilt source patch still needs the checks below.

Files: Shared metric failure renderer used by the Full Report Links table and metric cards. In 4.3.1-chrome-3-seobar/chunks/semrush-Ck9Hqxg5.js, it is li, exported as Q (formatted lines 3143–3156). Locate the source equivalent by Couldn’t load and its label/onRetry props; the older local checkout does not establish the new source filename. Do not patch generated bundles.

Historical specification below. The closeout above supersedes its former open status.

Low priority · Product revision · Both connection states

Issue: Both Links-tab Backlinks CTAs open a domain report, even when the user is analyzing an individual article. The original domain-preservation fix is complete and worked as specified. This revision makes the destination match the page being analyzed.

Fix:

• Use the analyzed report’s page URL for both connected and disconnected CTAs. Open /analytics/backlinks/overview/ with the encoded full URL in q and searchType=url. Use Exact URL scope, not domain or subfolder. Reuse the existing page-backlink URL handling; retain the meaningful path and query.
• Preserve the distinct connected/disconnected tracking through ctaConnectionTracking('backlink_analytics', connected), including report_backlink_analytics and the state-specific utm_content. Connection state changes the copy and possible sign-in gate, not the target page.
• Keep the current headings and buttons: connected “Now See Who Links Back” / “Open Backlink Analytics”; disconnected “Get Your Free Backlink Report” / “Check Backlinks”. Use the supporting copy below in both states.
• Keep the exact page selected after Semrush sign-in or signup. SEOquake connection and the website’s login session are separate states.

Approved supporting copy: See which sites link to this page, how authoritative they are, and where those links point.

Scope: The Backlinks CTA below Full Report → Links in both connection states. No changes to unrelated domain metrics, report-scope controls or other Semrush destinations.

Files: src/components/report/panels/LinksPanel.tsx and the existing Backlinks URL/tracking helpers. The reviewed package already uses searchType=url for page-backlink metric links.

Historical specification below. The closeout above supersedes its former open status.

CRO-07 · Low priority · Copy revision for 4.3.1

Completed: The Keyword data row, query/country destination and tracking are implemented. Package checks and live review passed.

Issue: The visible tooltip repeats the query already shown in Google. Remove it; keep the approved row and accessible description.

Fix:

• Remove the visible tooltip from “Keyword data”, including any browser title tooltip. Keep its descriptive accessible name, current query and new-tab information.
• Keep the existing label, icon, placement, destination, locale handling, tracking and keyboard focus unchanged.

Implemented design · reference

Visual: shipped 4.3.0 sidebar compared with the proposed row, for the query “what is seo”.

Captured from the shipped 4.3.0 package on a local Google results page at 2x; live Google was not loaded. The proposed row is built from the Export CSV row’s own markup, so its spacing, color, hover and focus classes match. The icon is the Semrush mark already used on result metrics.

Revision · October 21: Remove the Keyword data tooltip. Repeating the search query adds clutter because it is already visible in Google’s search field. Keep the row label and screen-reader description; no replacement tooltip copy is needed.

Label: the sidebar leaves about 88px for a row label at 13px. “Keyword data” (84px) fits. “Research keyword” (113px) and “Keyword Overview” (115px) would truncate. Keep the implemented label.

Preserved behavior: Hiding the row for queries with operators such as site: or inurl: is a product choice, not an approved requirement. Keep the implemented original-query behavior; do not strip operators as part of the tooltip revision.

Scope: One placement, in the expanded sidebar only. The collapsed tab is unchanged, and the row hides with the other tools when the SEOquake overlay is unchecked. No result-row or AI Overview keyword links in this ticket; measure this campaign before adding more placements.

Files: src/components/serp/SerpControlPanel.tsx; src/components/shared/parameters/ParameterControl.tsx; src/utils/semrush/utm.ts; src/utils/semrush/databaseCountry.ts.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: After Chrome stops the background worker, SEOquake can lose the page’s HTTP status and response headers. A captured 200 response becomes an error, and a page with X-Robots-Tag: noindex can appear indexable. The recorded chrome-5 test reproduced this after 30 seconds idle. The root cause also exists in 4.2.3.

Fix:

• Register network and tab-cleanup listeners synchronously. Preserve enabled and paused behavior while settings initialize; do not collect while SEOquake is paused.
• Keep the required network observations in session storage and restore them before answering report requests. Associate them with the correct tab and navigation. Clear closed-tab data and invalidate stale observations when the page changes.
• Distinguish a response that was not observed from an observed response with no robots header. Missing capture must not become an HTTP failure, an indexable verdict or a healthy summary count. Apply the same distinction to the combined Noindex result and PDF output.

Copy to confirm: The label and explanation for an unobserved response still need review. The required behavior is settled: do not show a definitive pass or failure without captured evidence.

Files: src/entrypoints/background.ts; src/utils/page/messaging/registerBackgroundNetworkHandlers.ts; src/utils/page/messaging/pageNetworkHandlers.ts; src/utils/page/cache/; network-dependent analyzers in src/utils/page/analyzers/.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: Common Yoast and Rank Math directives such as max-image-preview:large and max-snippet:-1 trigger warnings in Meta Robots and Noindex Tag. The shared parser also misses bot-scoped headers such as googlebot: noindex. These results misrepresent the page’s indexing directives.

Fix:

• Evaluate directive values and bot scopes in both parsing paths. Permissive max-* values should not trigger restrictive-directive warnings; do not blanket-allow every value.
• Preserve meaningful handling of noindex, none, restrictions and conflicts. A bot-scoped noindex must not produce an unqualified indexable result.
• Keep Meta Robots, X-Robots-Tag and Noindex Tag consistent. Preserve agent scope rather than silently applying one bot’s directive to every crawler.

Files: src/utils/page/analyzers/metaRobots.ts; src/utils/page/helpers.ts; src/utils/page/analyzers/noindex.ts; src/utils/page/analyzers/xRobotsTag.ts.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: The responsive-design check counts readable media rules. Cross-origin stylesheets are skipped, and a zero count produces a failure even when the viewport is valid. Responsive pages using CDN CSS, nested rules or fluid layouts without media queries can therefore fail this check.

Fix:

• Track whether the relevant stylesheets could be inspected and traverse accessible nested rules where supported.
• Do not infer a responsive-design failure from zero readable media rules. Cover unreadable CDN CSS and valid fluid layouts, not just the cross-origin exception.
• Use an inconclusive result when the available evidence cannot establish responsiveness. Keep the separate viewport findings; a valid viewport alone does not prove a responsive layout.

Status and copy to confirm: The inconclusive label and explanation still need review. Do not substitute an automatic pass or keep a false failure while choosing the wording.

Files: src/utils/page/collectors/responsiveDesign.ts; src/utils/page/analyzers/responsiveDesign.ts.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: The Analytics collector scans the entire page HTML for tracking-like IDs. Ordinary text such as G-20 summit can be treated as an invalid ID and make a valid Analytics setup fail. A valid GA4 ID plus this body text reproduced the false result.

Fix:

• Collect IDs from supported tracking scripts and configuration contexts. Do not treat arbitrary page copy as tracking configuration.
• Preserve supported GA4, Universal Analytics and Tag Manager detection. A malformed ID in an actual tracking configuration must still be identified; unrelated text must not override a valid setup.

Files: src/utils/page/collectors/analytics.ts; src/utils/page/analyzers/googleAnalytics.ts.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: Pages still load and compile the SEObar bundle when SEObar is off, SEOquake is paused or the page is excluded. The off and paused cases used about 6–7 ms of extension script work at normal CPU and 27 ms at 4×. The excluded-page check also used about 27 ms at 4×, with no visible bar.

Fix:

• Keep the initial script small. Check the current settings and page eligibility before loading the SEObar UI, styles and other expensive dependencies.
• Verify the packaged output actually keeps that UI separate. The existing dynamic import is inlined into the shipped bundle, so changing the source import alone is not enough.
• Preserve settings changes, pause/resume and navigation in already-open tabs. If changing content-script registration, account for scripts already injected into those tabs.

Expected benefit: Less repeated processing where the bar will not appear. The measured script time is a target to reduce, not guaranteed page-load savings.

Files: src/entrypoints/seobar.content.ts; src/utils/seobar/visibility.ts; src/utils/seobar/urlFilters.ts; src/utils/seobar/watchPageUrl.ts; packaged content-scripts/seobar.js.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: Broad network listeners observe requests across tabs and resource types. On the 300-image test page, the worker received 2,505 messages with SEOquake enabled and 2,431 with SEObar off. Worker processing was 26.1 ms and 23.5 ms respectively. These are messages, not separate worker starts.

Fix:

• Map each listener to the report evidence that needs it. Narrow request types, URLs and collection lifetime where that evidence can still be captured correctly. Restrict redirect tracing to the requests that need it.
• Coordinate this with the 4.3.1 network-observation fix. Preserve synchronous listener registration, session restoration, tab/navigation ownership and unknown-state handling.
• Retain original navigation status, response headers, redirects and required image evidence. A later fetch is not a substitute for the original response, especially on authenticated pages. Keep permission removal or optional-permission changes out of this fix.

Expected benefit: Less background work on pages with many requests. The exact reduction needs a candidate build; the independent run did not isolate each listener's cost.

Files: src/utils/network/redirectCapture.ts; src/utils/page/messaging/registerBackgroundNetworkHandlers.ts; src/utils/page/messaging/pageNetworkHandlers.ts; src/utils/page/cache/mainFrameNetworkCache.ts; src/utils/page/cache/imageResponseSizeCache.ts; src/entrypoints/background.ts.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: The verified ten-result fixture added about 582 ms of page processing and 95 ms of blocking time at 4× CPU throttling. All ten overlays rendered in each extension run. The SERP bundle also loads on Google pages where there are no web results. These measurements describe browser processing, not the size of a rebuild or guaranteed page-load savings.

Fix: Investigate before choosing the rendering changes. Separate the small page-eligibility check from expensive results UI. Profile startup, overlay creation, repeated rendering and rescans to find the dominant costs. Propose a targeted change that keeps the existing design and functionality. The fixture confirms overhead; it does not establish the best rendering fix.

Coverage to complete: Test real Google results and AI Overview with Semrush connected and disconnected. Google served a verification challenge during the independent live check. Authentication succeeded, but the connected timing harness failed before recording measurements. Windows and lower-memory hardware remain untested.

Files: src/entrypoints/serp.content.tsx; src/utils/serp/syncOverlays.ts; src/utils/serp/google/match.ts; src/utils/semrush-connected/cache.ts; packaged content-scripts/serp.js.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: Connect Semrush opens Settings → Integrations before users can start connecting. The connection card asks whether they already have an account, while the signup prompt still promotes Semrush One. Remove the extra settings step and give new users a clear free-account option.

Fix:

• Start the existing OAuth flow directly from connection CTAs in Quick View, Full Report and the first-result SERP teaser. Reuse startSemrushAuth() through the existing connection flow instead of the Settings navigation callbacks. Keep source-tab context for returning to the report. Keep Settings available for managing or disconnecting the account.
• Require an explicit click. Preserve the random, single-use authorization state, its 10-minute expiry, callback validation, existing scopes and token handling. Do not hard-code a standalone authorization URL or expose credentials to the host webpage.
• Keep the original page/report available. Prevent duplicate starts throughout authorization, handle cancellation and failure with a retry option, and refresh connection status and metrics after success. The existing useSemrushConnection hook’s busy state covers launch only; opening OAuth is not a completed connection.
• Apply the approved copy below to the shared connection card in Quick View and Full Report. Replace the associated Semrush One signup promotion with the free-account link. Keep the existing layout and responsive behavior. The compact SERP teaser keeps its current copy for this ticket; only its Connect action changes.
• For signup links, add signup to SemrushDestination and use destination: 'signup', placement: 'cta', panel: 'semrush' with the shared Link helper. Use /signup/; generate popup_signup or report_signup by surface, preserving the attribution fields below.

Approved copy:

• Headline: See Authority Score, visits and engagement data
• Body: Connect a free Semrush account to see these metrics.
• Button: Connect Semrush
• Line below: New to Semrush? Create a free account

Signup link and tracking: Use https://www.semrush.com/signup/. Add signup to the shared tracking destinations. Keep utm_source=seoquake, utm_medium=toolbar, utm_content=semrush_cta and ref=174537735. Use utm_campaign=popup_signup in Quick View and report_signup in Full Report. Remove the old semrush_one destination from these signup links so the helper does not overwrite the new campaign. Do not change unrelated promotions or add these signup UTMs to the OAuth URL.

Scope: Signup creates an account; Connect authorizes SEOquake to use it. Verify the new-account journey and available free-account metrics before shipping this copy. Do not imply unlimited data access. The approved first-result lock icons are covered by the separate teaser ticket, and the header status entry point by the status ticket.

Files: src/components/shared/semrush/LockCta.tsx; src/components/popup/panels/SemrushPanel.tsx; src/components/report/panels/SemrushPanel.tsx; src/components/serp/overlay/SerpConnectedMetrics.tsx; src/hooks/useSemrushConnection.ts; src/utils/semrush-auth/messaging/authHandlers.ts; src/utils/semrush-auth/oauthState.ts; src/utils/semrush/utm.ts.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: When Semrush is disconnected, the first organic result shows placeholder zeros for Authority Score, Visits, Pages/Visit, Avg. Visit and Bounce Rate. These are not measured values. They can make the result look like it has no authority or traffic instead of showing that an account connection is needed.

Visual: shipped 4.3.0 compared with the proposed locks, on result 1 with the top of result 2.

Captured from the shipped 4.3.0 package on a local Google results page at 2x; live Google was not loaded. The proposed frames change only the five disconnected values: each becomes the repository’s lock.svg at 12px in the label colour, and the AS gauge is removed. Screen readers would hear “Authority Score: connect Semrush to view” instead of a zero.

Connected reference: an actual Authority Score of 0 keeps its numeric value and gauge. Zero traffic already displays n/a, because formatTrafficMetrics (src/utils/semrush-connected/trafficAnalytics.ts) treats visits of 0 or less as no data.

Fix:

• Replace those five disconnected placeholder values with small lock icons. Keep the metric labels, order, existing strip styling and connection prompt. Show this teaser only on the first organic result, as it does today.
• In ConnectedMetric, select locks only for status === 'disconnected'. Keep SerpOverlay’s first-result visibility rule. Do not use a zero-value or falsy-value check. Leave formatTrafficMetrics unchanged and preserve existing connected-value formatting: Authority Score 0 stays numeric with its gauge; zero or unavailable visits retain the traffic formatter’s n/a behavior.
• Gate the Authority Score gauge with !disconnected && score != null so the teaser does not imply a measured score of zero. Keep the gauge and its normal behavior for actual connected scores, including 0.
• Use lock.svg at 12px in the label colour, matching the mockups. Provide accessible text such as “Authority Score: connect Semrush to view” for each locked metric; do not announce a numeric zero. Preserve existing tooltip keyboard access and verify visibility in light and dark themes.
• Keep the icons non-interactive. The existing Connect CTA remains the action, with direct OAuth covered by the connection-flow ticket. No extra sign-in controls or permission changes are needed.

Scope: Only the disconnected connected-metrics teaser on the first organic result. Leave the separate SE Traffic and other standard metrics unchanged. Preserve connected values, missing-data labels, loading indicators and retry behavior. Disconnected AI Overview cards currently omit Authority Score; do not add locks or change their layout as part of this ticket.

Files: src/components/serp/SerpOverlay.tsx; src/components/serp/overlay/SerpConnectedMetrics.tsx; src/assets/icons/lock.svg. Keep the change scoped where shared metric components are reused.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: Quick View, Full Report and Settings show “Disconnected from Semrush” in the header, but the status is a static element (SemrushStatus.tsx). Users who notice it have to find a Connect button elsewhere. The status is the one connection cue that appears on every surface.

Fix:

• Make the header status a button. While disconnected, it starts the direct OAuth flow from the connection-flow ticket, using the same handler and duplicate-start guard. While connected, it opens Settings → Integrations, the same destination as the Settings menu’s Manage Semrush connection row.
• Keep the dot, label and header layout. The pause switch and Settings button keep their positions.
• Show that it is interactive on the dark header: pointer cursor, mint #18F0BF text on hover and keyboard focus like the other header controls, and a visible focus ring. Add the tooltip “Connect your free Semrush account” while disconnected and “Manage Semrush connection” while connected.
• Use the accessible names “Connect to Semrush” and “Manage Semrush connection”, matching the Settings menu. Where the label is hidden at narrow widths, keep the dot inside a padded button with the same accessible name. Match the other header controls’ hit area; do not make the 6px dot the entire click target.

Scope: The header status only. If the connection-flow ticket does not ship in the same package, the disconnected status opens Settings → Integrations instead, like today’s Connect paths. Add no UTMs to the OAuth URL.

Files: src/components/shared/layout/header/SemrushStatus.tsx; src/components/shared/layout/Header.tsx; src/hooks/useSemrushConnection.ts. Reference: src/components/shared/layout/header/SettingsButton.tsx.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: In Full Report → Semrush → Traffic Analytics, Monthly Visits opens Traffic Analytics for the current domain, but Unique Visitors opens the generic https://www.semrush.com/analytics/traffic/ landing (TrafficAnalytics.tsx, trafficAnalyticsBaseUrl). Users who click Unique Visitors have to enter the domain again.

Fix:

• Link Unique Visitors to trafficFullReportUrl(domain), the same /analytics/traffic/overview/?q=<domain> destination as Monthly Visits. Its overview page leads with Unique Visitors.
• Keep metricTracking('traffic_analytics', 'unique_visitors'), so the link keeps utm_content=semrush_metric_unique_visitors and stays distinguishable from Monthly Visits.
• Leave trafficAnalyticsBaseUrl for its other, non-domain uses.

Scope: The Unique Visitors card in Full Report only. Quick View’s Traffic Analytics cards open Full Report and are unchanged. Context: report_traffic_analytics, which covers both links, recorded 192 visits and 7 registrations from August 10 to October 4, 2026; the data does not split by utm_content.

Files: src/components/report/panels/semrush/TrafficAnalytics.tsx. Reference: src/utils/semrush-connected/deepLinks.ts.

Reviewed 4.3.1 chrome-2-perf · Closed October 26, 2026

Issue: In Full Report → Links, the connected Backlinks CTA opens the current domain’s Backlinks report (/analytics/backlinks/overview/?q=<domain>&searchType=domain), while the disconnected CTA opens the generic /analytics/backlinks (LinksPanel.tsx). Disconnected users lose the site they were analyzing.

Fix:

• Point the disconnected CTA to the same domain-specific destination as the connected CTA. Encode the domain.
• Keep its tracking (ctaConnectionTracking('backlink_analytics', false)), so connected and disconnected clicks stay distinguishable.
• Ship only if the journey check below passes. If Semrush drops q during signup or sign-in, keep the current link.

Journey check: In a signed-out browser, open the proposed URL, create a free account, and sign in with an existing account. Both paths should end on the Backlinks report for that domain.

Scope: The disconnected Links CTA only. The connected destination and its tracking are unchanged; choosing a different Backlinks report is a separate decision. Context: report_backlink_analytics recorded 1,350 visits and 49 registrations from August 10 to October 4, 2026, for both states combined.

Files: src/components/report/panels/LinksPanel.tsx.

Implemented in chrome-4: Internal/External occurrence counts and destinations, clickable Words in Page Info and Content, and the Full Report sections dropdown. Loaded-extension checks confirm the four tile routes, report reuse, menu coordination and focus restoration. The original navigation implementation is complete; the two follow-ups below remain.

Issue: Both Words tiles lack a hover/focus description of their Keyword Density destination. Page Info’s seven-column strip also truncates larger values: 10,028 displays as 10,0… at native popup size, while Content shows the full count.

Fix:

• In PageSummary.tsx and ContentSummary.tsx, add buttonTooltip: 'Open Keyword Density' to the words item. Reuse BoxValue’s existing button tooltip; preserve the blue value, full-tile action and openReportFromPopup(reportSourceTabId, 'density') routing.
• In PageSummary.tsx, replace grid-cols-7 with grid-cols-[repeat(7,minmax(max-content,1fr))] and change the strip’s valueClassName from block w-max max-w-[calc(100%+12px)] truncate text-left to block text-left. Columns share the available space until a label or value needs more room. Keep the 16px tile padding, typography, dividers and full-tile actions; Content’s five-column layout stays unchanged. Do not add ellipses or abbreviate counts.

Known limit: Combined large counts—for example, multiple four- or five-digit counts alongside six-digit Words—can exceed the available width. This limit is accepted for 4.3.0; no compact fallback is planned.

Files: src/components/popup/panels/page-info/PageSummary.tsx, src/components/popup/panels/content/ContentSummary.tsx. Reference: src/components/shared/box/BoxValue.tsx and src/utils/surface/navigation.ts.

Original proposal screenshots retained for reference; the interactive previews above show the latest Settings grouping. Renderings are design references, not proof of implementation.

Earlier requirements retained as history. The remaining Fix and Engineering checks above define the current work.

Issue: Quick View combines Internal and External links into one count, Words has no action in Page Info or Content, and Compare has no direct shortcut. Legacy users previously reached these reports from the popup’s top navigation.

Fix:

• In PageSummary.tsx, replace links with Internal and External. Use pageData.links.filter(link => link.internal).length and pageData.links.filter(link => !link.internal).length so counts match the report’s total occurrences. Route them through openReportFromPopup(reportSourceTabId, 'links', 'internal') and the corresponding 'external' call.
• In PageSummary.tsx and ContentSummary.tsx, add button: { onClick: () => openReportFromPopup(reportSourceTabId, 'density') } to words, reusing BoxValue’s blue value and full-tile action. Use grid-cols-7 in Page Info; keep Content’s grid-cols-5. Preserve Images and H1–H4 destinations.
• In NavButton.tsx, add a separate chevron beside View Full Report, gated to isPopup. Reuse Dropdown with panelTitle="Full Report", its existing aria-haspopup="dialog" / role="dialog" semantics, and ordinary navigation buttons. Use REPORT_PANEL_IDS in order with the report’s icons; each row calls openReportFromPopup(reportSourceTabId, panelId). Keep rows label-only and separator-free; omit divide-y / divide-gray-light from the report list.
• Preserve the label’s getReportTargetFromPopupTab(currentPanelId) routing and Header’s !isEmptyState visibility condition. Coordinate dropdown state through open / onOpenChange so Settings and Full Report cannot remain open together. Move focus into the dropdown on opening and return it to the chevron on Escape or Close; keep the shared dropdown’s other callers unchanged.

Files: src/components/popup/panels/page-info/PageSummary.tsx, src/components/popup/panels/content/ContentSummary.tsx, src/components/shared/layout/header/NavButton.tsx, Header.tsx, SettingsButton.tsx and src/components/shared/Dropdown.tsx. Reference: src/utils/surface/navigation.ts.

Implemented in chrome-4: Header switch, Settings Enable checkbox, shared Pause/Resume state, pending guard, confirmed-state reconciliation and persistent retry feedback. Tested loaded-extension flows cover successful and failed saves, retry, repeated activations, preserved display-toggle values and loading failure. Settings spacing and What’s New dismissal work; only the design follow-ups below remain.

Issue: Settings still separates Preferences, Semrush connection and About with individual lines. Its panel starts 16px below the header, while Full Report starts 8px below it.

Fix:

• In SettingsButton.tsx, wrap the popup’s Preferences, Semrush connection and About SEOquake in one navigation group. Keep divide-y on the three-group container only: Enable SEOquake; Show SEObar / Show SERP Overlay; navigation. Keep the outer border and exactly two group separators.
• Set the popup Settings panel to an 8px gap below the header, matching Full Report. Replace its scoped mt-4 panel override with mt-2, and verify the final geometry. Keep horizontal alignment, 16px padding, the 12px title gap and 34px navigation rows.

Files: src/components/shared/layout/header/SettingsButton.tsx. Reference: src/components/shared/Dropdown.tsx. Gate spacing changes to popup Settings; preserve Full Report/Settings surfaces and other dropdown callers.

Earlier requirements retained as history. The remaining Fix and Engineering checks above define the current work.

Issue: Pausing requires opening Settings → Preferences → General. Quick View’s Settings menu only offers separate SEObar and SERP Overlay controls, making the global pause setting harder to find.

Fix:

• Add a popup-only switch between the Semrush status and Settings, with a 36 × 32px hit area. Use mint #18F0BF with a dark #181E15 knob when enabled, and grey #60636B with a white knob when paused. Keep the accessible name Enable SEOquake, update aria-checked, and show Pause SEOquake or Resume SEOquake on hover and focus.
• Add Enable SEOquake as the first Settings checkbox, in its own group above the two display toggles. Make each checkbox’s full row clickable. Use 16px panel padding, 12px below the title and 34px navigation rows. In SettingsButton.tsx, group Preferences, Semrush connection and About SEOquake in one wrapper; use divide-y between groups only. Keep these changes local to this menu.
• Give What’s New a plain wrapper with 9px top padding and a 24px gap from the menu box. Align its heading with the first menu row and use the approved 4.3.0 copy. Preserve scrolling; Got it dismisses the notes while keeping Settings open at its single-column width.
• Share enabled, pending and error state across the switch, Settings checkbox and existing Resume button. Save only general.enabled, keep the controls synchronized and prevent stale reads from restoring an older state. Disable pause controls during loading or saving; keep them disabled if loading fails.
• On a failed save, restore the confirmed state and show “Couldn’t pause SEOquake.” or “Couldn’t resume SEOquake.” with Try again below the header. Keep the notice visible across normal and paused states. Apply failure reconciliation to Full Report’s existing Pause/Resume too.
• Keep the existing paused screen and Settings access. Preserve saved SEObar/SERP choices, disabling their controls during saving and while paused. Keep native navigation, Settings positioning and empty-state behavior; shift the Semrush status 48px left. Full Report and Settings headers stay unchanged.

• The shared public-request helper forces credentials: 'omit' after ...init and removes Cookie, Authorization and Proxy-Authorization headers. Deliberate Semrush OAuth authorization stays separate. The social image preview now uses this helper.
• Link-status checks no longer start when Quick View or Full Report opens. The shared flow is opt-in, with a Check status button in Links.
• Collected admin-bar links are marked and skipped. The expanded action policy runs in both frontend and background paths before cache lookup, before requests and at redirects.
• Status and cache keys preserve query strings, so /cart/ and /cart/?empty-cart=1 cannot share a query-stripped result.
• Link responses with 401/403 show warnings and are excluded from Broken totals. Skipped links are neutral in the Links table. Unchecked and all-skipped Audit sets show a warning. Additional inconclusive classifications follow in 4.2.3.

Completed from the chrome-4 review:

• Load the social share preview image (og:image or twitter:image, in Quick View’s Schema tab and the Full Report’s Audit) through the same anonymous helper, apply the same skip rules, and render the returned data URL. Direct <img src> loads can send the site’s cookies. Show the placeholder when the image is skipped.
• The action-URL policy now covers both frontend and background paths, including session and download parameters, names containing nonce or token, and the action words below. Removing cookies alone isn’t enough when the URL carries a session or token. Keep these minimum exclusions:
  • WordPress: any path ending in /wp-login.php or another /wp-*.php file, any path containing /wp-admin/ (covers subdirectory and multisite installs), and links inside #wpadminbar, marked when links are collected.
  • Session and token parameters: sid, PHPSESSID, jsessionid, osCsid, zenid, key, token, hash, sig, signature, download_file, download_key, eddfile, empty-cart, remove_item, any parameter name containing nonce or token, and a ;jsessionid= path parameter.
  • Action words: a path segment or parameter value of logout, log-out, logoff, signout, sign-out, unsubscribe, confirm, verify, activate or reset-password. Treat an action parameter as an action only when its value is one of these, or when the URL also carries a nonce or token.
  Match parameter names case-insensitively, after percent-decoding. Apply the rules before cache lookup, before requests and at each redirect. Preserve query strings in status and cache keys. Keep these links in the report, labeled Skipped.
• The Audit now requires completed eligible checks before a pass. Unchecked or all-skipped sets show the existing warning state, not a healthy pass. Keep the existing link 401/403 warnings and neutral skipped-link handling. Policy-skipped links stay listed but don’t block a pass when eligible checks are complete. Keep link counts and structural findings available. Genuine 404/410 and server errors still fail.

CSV compatibility: chrome-5 restores the existing numeric Status column, with n/a when no HTTP status is available. The new Check result column is implemented in the 4.2.3 candidate.

The installed WordPress run covers the normal flows above. The full checklist below remains the regression reference; hostile image and redirect cases have extracted-code coverage, not installed-browser proof.

• On staging WordPress with a logged-in admin bar, open Quick View and Full Report, then open Links and press Check status. The user stays logged in and action links show Skipped. Exercise eligible HEAD-success and HEAD-to-GET checks, and confirm excluded action URLs are never requested.
• Network logs show no requests to excluded action URLs, including through redirects. Eligible public checks send no website Cookie or Authorization credentials and don’t apply Set-Cookie responses. Safe public redirects and existing private-address guards still work.
• Opening Quick View, Full Report or its Links tab sends no automatic link-status requests. The Links button starts eligible checks and shares the results with the Audit.
• These links are all Skipped and never requested: a phpBB-style ucp.php?mode=logout&sid=…, a WooCommerce download_file link, an Easy Digital Downloads download_key link, an uppercase or percent-encoded nonce parameter, and a subdirectory /blog/wp-login.php.
• With /cart/ already checked, /cart/?empty-cart=1 shows Skipped, not the cached result.
• With og:image set to the logout URL, opening the Schema tab and the Audit neither logs the user out nor requests that URL with cookies. Public og:image and twitter:image previews still render.
• Before checking, and with every link Skipped, the Audit shows a warning rather than a healthy pass. Link 401/403 results keep their warnings and stay out of Broken totals. Eligible working links can still pass with skipped admin-bar links present. Real link 404/410 and genuine server-error failures still fail; existing structural findings remain.
• Export before checking and after mixed results. Status keeps numeric HTTP codes or n/a, without descriptive labels mixed into that column. Unchecked and skipped rows remain exportable without starting checks.

Original guidance:

• Finish neutral handling across the Audit, Links table and totals. Keep the existing 401/403 handling and add 429, recognized login redirects and positively identified bot challenges. These results count as neither broken nor healthy. Carry skip or login-redirect reasons and the challenge indicator through response types and hooks. Identify challenges only with supporting evidence, such as cf-mitigated: challenge, never from a 503 alone. Preserve available HTTP codes.
• Apply those rules to robots.txt and sitemap checks. Anonymous 401/403/429 responses, stopped login redirects and confirmed challenges show warnings. Carry the reasons and positive challenge indicators through page-network results. Keep existing missing-file and structural checks, and genuine server-error failures.
• Finish the shared check flow. Keep the existing opt-in behavior and add the trigger on the Audit’s Internal Links row. Label both buttons Check link status and use the same results. Preserve the 4.2.2 neutral classifications and pass safeguards. Finish the Not checked, Checking and Needs review states. Keep link counts and structural findings available. If no links are broken but some couldn’t be checked, show “N links couldn’t be checked.” Policy-skipped links don’t trigger Needs review. Independently verified failures still fail.
• Add clear labels to the 4.2.2 results. Use Authentication required for 401, Couldn’t check (HTTP 403) when the refusal’s cause is unknown, and Rate limited (HTTP 429). A recognized login redirect shows Login required (redirect). Use the existing challenge indicator to label confirmed bot protection. Preserve available HTTP codes and apply the labels consistently in the Audit, Links table and totals. For robots.txt and sitemap 401 or recognized login redirects, add the warning Not public to anonymous visitors (HTTP N). Other inconclusive results keep their matching reason. Genuine server errors remain failures.
• Add the CSV Check result column for the matching label, preserving the numeric Status format restored in 4.2.2. Use n/a when no HTTP status is available. Not checked and Skipped rows must remain exportable without starting link-status checks.

Remaining installed-browser checks:

• Opening Full Report, or its Links tab, sends no automatic link-status requests. Either button starts the checks and updates both views.
• Unchecked or inconclusive results never produce a healthy-link pass. Inconclusive checks alone show Needs review, rather than “fix broken targets.” Policy-skipped links, including the admin bar, don’t block a pass or trigger Needs review.
• Test working links, 404/410, 401, an unexplained 403, 429, a recognized login redirect, a confirmed challenge and a server error. Labels and totals agree; excluded redirect destinations are never requested.
• Robots.txt and sitemap checks show a warning for anonymous 401/403/429 responses, a stopped login redirect or a confirmed challenge, including a 503 with a positive challenge indicator. A 401 or recognized login redirect uses the Not public warning. An unexplained 503 remains a server error. Existing missing-file and structural findings remain.
• Export before checking and after mixed results. The CSV preserves HTTP codes, carries the matching labels and includes unchecked and skipped rows.

Files: src/utils/network.ts, src/utils/links/status.ts, src/utils/messaging/links.ts, src/utils/links/types.ts (response indicators and UI states), src/utils/messaging/pageNetwork.ts, src/utils/page/collectPageNetworkData.ts (robots and sitemap indicators), src/utils/page/analyzers/linksInternal.ts (classifications and states), src/utils/links/exportCsv.ts (Check result column), src/components/report/panels/LinksPanel.tsx (Audit trigger and shared results), src/components/report/panels/links/LinksTable.tsx and src/components/report/panels/links/LinksOverview.tsx (classifications and labels), src/utils/page/analyzers/robotsTxt.ts and src/utils/page/analyzers/sitemap.ts (warnings), src/hooks/usePageData.ts, src/hooks/useLinkStatuses.ts and the Full Report link-check trigger.

Original issue: turning off the overlay required opening Preferences or using the Google sidebar. The new control uses the same checkbox style and existing serp.enabled preference.

Verify: it toggles the overlay, stays synced and saved, and leaves other preferences unchanged.

• Reuse serp.enabled. Keep saved metrics, AI-source and sidebar-collapse choices. Disable the control while settings are loading or unreadable; don’t show a failed save as saved.
• Check off/on against an open Google results page without reloading, then reopen Quick View and restart Chrome. Changes from the sidebar or full Settings must agree. Rapid SEObar and SERP Overlay changes must both persist.
• Check keyboard access, a failed save and popup fit with and without What’s New.

Files: src/components/shared/layout/header/SettingsButton.tsx, src/hooks/useAppSettings.ts and the existing settings save/watch flow.

Verify: check the number on light and dark Google pages, then toggle numbers off/on; check short and wrapped titles, the next results page and results added or removed dynamically. The number matches the title’s typography and first-line baseline; wrapped lines can use the full title width below it. Numbers agree with the existing result positions and CSV, without duplicates or counting ads/AI source cards. Clicking either the title or number opens the same result; mouse and keyboard navigation stay usable. Check that the screen reader’s link name remains clear. Test on the identified rebuilt extension; this comparison is a mockup.

Files: src/components/serp/overlay/SerpStandardMetrics.tsx, the SERP host mount/update/cleanup flow and Google title placement in src/utils/serp/google/insert.ts. Reuse showPositionNumbers and the existing result position data.

Verify: on light and dark Google pages, test Match Google and both overrides, including a page theme that differs from the computer’s setting. Change Google’s theme without reloading. Confirm numbers remain readable with the opposite overlay theme. Check wrapped titles, connected/disconnected metrics, AI cards, the source panel, tooltips, hover and keyboard focus. Reopen Settings and restart the browser to confirm the saved choice; check the default, Reset and existing autosave failure/retry behavior. SEObar settings, values, destinations and exports remain intact.

Files: reuse SEObar’s existing theme colors in the SERP styles and shared metric components, with the top-row shade specified above. Add the SERP Appearance choice through the existing settings control, preferences defaults/normalization and autosave flow. Apply Google theme detection and the saved override at the SERP host, including its separate shadow roots. Keep title-number contrast tied to Google’s background and preserve its accepted placement and lifecycle.

Package evidence: the draft/applied split and cross-tab reset are present in the supplied 4.2.3 and 4.3.0 packages. The proposed autosave fix still needs rebuilt-package checks.

• Toggle several parameters quickly, close the menu, switch tabs and reload. The final choice stays applied and stored. A change made from Settings agrees with the report menus.
• Force a save failure, keep editing and retry. Reset Internal while External has a pending or failed edit, then reverse the tabs. Only the reset section returns to defaults; stale writes and refreshes cannot undo either section’s latest choice.
• Run Compare, then enable a metric whose request group was not attempted. Its row shows the load hint until the next run. Also enable a metric from a group already fetched: retain its value. Failed requests and unavailable results must keep their existing states rather than showing the never-requested hint.

Package evidence: controlled rendering confirms overflow in both supplied packages. The proposed 4.3.0 Anchor Text fix fits the reviewed Internal defaults; it does not make External defaults or every metric fit without scrolling.

• Confirm the rebuilt stylesheet emits max-w-0 and both ordinary and expanded duplicate Anchor Text cells compute to max-width: 0px.
• Check both Links tabs with only Backlinks visible at the reviewed 898px inner frame width. Include long anchors, expanded duplicates and long Check result labels. Anchor Text retains at least 160px; the table fits before and after checking.
• Check External defaults, all metrics and narrower windows. Horizontal scrolling reaches the last column without overlapping text. Sorting, links and CSV export retain their existing behaviour and full values.

Comparisons from the October 8 review of the October 7 package. The supplied 4.3.0 chrome-2 package still has both overrides, checked October 12. Revised mockups show the intended colors; they do not show a shipped fix. Click any screenshot to open the original full size.

Installed screenshots · October 12

Package evidence: computed colors and contrast calculations confirm the issue in both supplied packages. #2154CC raises normal-text contrast from 3.87:1 to 5.51:1 on lavender #F2E7FF, and from 4.07:1 to 5.79:1 on blue #EBF1FF.

Verify: both Quick View tip CTA variants and the Audit Tips links compute to #2154CC in the rebuilt package. Heading level tags compute to #60636B in Quick View and Full Report. Check hover and keyboard focus, then confirm white-background links retain #2969FF.

Implementation evidence: the shared Link component forwards its class to the anchor. The latest supplied chrome-2 package still has the global link and heading overrides; it requires these targeted fixes and rebuilt-package checks.

Historical comparisons from the October 8 design review. The supplied 4.3.0 chrome-2 package still has the same stacking mechanism, checked October 12. The proposed capture demonstrates the fix; it does not show a shipped implementation. Click a screenshot to open the original full size.

Package evidence: the latest supplied 4.3.0 chrome-2 package has the unisolated tile root and raised tooltip anchors. Controlled rendering confirms that isolation contains the icon stacking. The shared tooltip bubble is portaled outside the tile.

• In Internal and External Links, open Add/hide parameters with the toolbar in its normal and stuck positions. No overview icon paints over the menu or toolbar; each toolbar control still receives clicks.
• Verify tile tooltip hover, then check shared interactive tiles with mouse and keyboard. Existing actions, focus outlines and tooltip behavior remain usable; the fix does not turn Links tiles into actions.
• Confirm the rebuilt stylesheet includes isolation: isolate and the root computes to isolation: isolate. Check Quick View and Full Report wherever BoxValue is shared.

User-supplied October 12 captures of the observed appearance, retained unchanged. They are references for the issue, not examples of an implemented fix; the screenshots do not display the installed version. Click any image to open the original full size.

Package evidence: the supplied 4.3.0 chrome-2 package contains the same BoxValue inline last-word wrapper and Tooltip anchor classes. Its stylesheet declares text-13 as 13px, text-12 as 12px and --spacing: 4px, making size-3.5 14px. The SVG's intrinsic 16px dimensions are overridden by size-full. Reviewed source: origin/4.3.0 at ce65ab66263f51431a453e8fa126dbedd9e446ff.

• Rebuild and inspect Quick View's Semrush cards, Full Report's Domain Metrics, Backlinks Overview and Traffic Analytics, and Keyword Overview's Total words. Icons should visually align with the adjacent label text, with no downward drift.
• Check ordinary desktop width, narrow cards and browser zoom. Use both short labels and labels that wrap to two lines. The icon remains with the final word; the text keeps its normal wrapping and does not overlap the value, clip or force card overflow.
• Verify computed label font sizes remain 12px / 13px, tooltip and SVG boxes remain 14 × 14px, and the left margin remains 4px. Confirm the generated stylesheet includes [&>svg]:-translate-y-[2px]; the SVG moves up exactly 2 CSS pixels while the anchor and inline last-word wrapper retain their current geometry.
• Hover the info icons and activate existing card links/buttons with mouse and keyboard. Tooltips, destinations and focus outlines still work. Section headings retain their current alignment; the separate isolation fix still keeps icons behind the Links toolbar and Parameters menu.

Local visual evidence: same-document comparisons of native Quick View, Domain Metrics (including wrapped labels), Backlinks Overview, Traffic Analytics and Keyword Overview confirm the SVG-only lift improves alignment without moving labels, values, cards or headings. The flex alternative reduced Quick View's line-box height by 0.125px and was dropped.

Verification boundary: these are package-rendered previews with frozen fixtures. The proposed SVG-only change still needs visual and interaction checks in the rebuilt extension.

Historical comparison from the October 8 design review. The supplied 4.3.0 chrome-2 package still uses two lists, checked October 12. The revised mockup shows the intended order, not a shipped fix. Click a screenshot to open the original full size.

Package evidence: the latest supplied 4.3.0 chrome-2 package chooses between POPUP_KEYS and SNAPSHOT_KEYS. Using one order matches the accepted design correction.

• Quick View and Full Report read Canonical, Robots.txt, Schema.org Markup, URL. At the report’s two-column width, Canonical and Robots.txt occupy the first row, with Schema.org Markup and URL below.
• Check compact Quick View, the two-column report and a narrow single-column report. Dividers appear once at each shared edge; values, links and shortened popup Schema text keep their existing behavior.

Verify: the rebuilt 4.3.0 package contains both lines exactly, including their [+] and [*] prefixes. In Quick View Settings, both lines, View all updates and Got it remain fully visible; text wraps within the What’s New column without clipping.

Original issue: Google adds srsltid to some result URLs. The SERP’s URL Backlinks metric and its Semrush link keep that parameter, so they look up the tracking variant instead of the page. Analyze already removes it.

Observed Sep 30 · chrome-5: the SERP export shows 0 URL backlinks for GoodRx, Segafredo and Ember Coffee. The AI-source exports use the same pages without srsltid and show 26, 17 and 1. The supplied GoodRx and Segafredo backlink links also include srsltid in Semrush’s q value. These are snapshot values, not targets to hardcode.

Original guidance:

• Use the same cleaned page URL for the URL Backlinks lookup, its cache key and its Semrush click-through link. Share the existing Analyze cleanup rather than adding a second set of rules. Cover the SERP strip, AI source cards and Analyze sources panel, plus other consumers of the shared backlink helpers.
• Remove known tracking parameters and fragments only. Keep the protocol, host, trailing slash and parameters that identify the page, such as YouTube’s v, product IDs and pagination. Keep domain and subdomain backlink scope, tracking attribution and result numbering unchanged.
• Keep the original result URLs in CSV and export the corrected backlink count. Use the cleaned URL only for Semrush analysis. Navigation and link-status/security checks must keep their original URLs, query strings and action exclusions.

Verify: with and without srsltid, the same page uses one backlink target and shows the same count in the strip, AI sources and CSV. Clicking URL Backlinks opens that cleaned page in Semrush’s URL mode. Identifying parameters still select distinct pages.

• Reuse Analyze’s current cleanup: srsltid, utm_*, gclid, dclid, fbclid, msclkid, mc_cid, mc_eid, _ga and _gl, matched case-insensitively, plus fragments. Preserve unknown parameters. Remove t only on YouTube, as Analyze does today.
• Compare fresh lookups for the linked GoodRx and Segafredo pages with and without srsltid. Confirm a cached tracking-variant zero cannot replace the cleaned page’s result. Check the API target, metric, click-through q and CSV count agree; current Semrush numbers may have changed.
• Check a trailing-slash page, HTTP and HTTPS, a www host, YouTube v, a product ID and pagination. Distinct identifying queries must retain separate backlink targets and cache keys. Domain/subdomain links and the existing serp_backlink_analytics / serp_metric_backlinks attribution remain intact.
• Retest a token-bearing action URL after adding the shared cleaner. The original URL must still be Skipped by security checks and never requested. Do not change the security URL normalizer or query-preserving status cache.

Files: src/utils/parameters/semrushBacklinks.ts, src/utils/parameters/helpers.ts and the backlink cache/handler, src/utils/semrush/metricLinks.ts, the Analyze cleanup in src/utils/semrush/overviewLinks.ts, and the SERP/AI metric and CSV consumers.

Earlier requirements retained as history. The remaining Fix and Engineering checks above define the current work.

Implemented October 13: The sidebar, Parameters menu and locale fields now follow the saved SERP theme. Package review and Beatus’s live review confirm the dark appearance. Keyboard-focus styling remains open.

Issue: Parameters, Export CSV, Country and Language can receive keyboard focus without a visible indicator. Collapse/reopen use dark green instead of the specified mint. Locale has a visible blue outline in the supplied screenshot; it needs the same dark-theme focus treatment.

Fix:

• Add a visible 2px mint #18F0BF keyboard-focus outline in dark mode to Parameters, Export CSV and both native locale selects. Replace outline suppression with an explicit :focus-visible treatment.
• Apply the same dark-mode focus treatment to collapse/reopen and Locale. Check the remaining sidebar and Parameters-menu controls for a visible, consistent indicator, including the overlay checkbox, parameter checkboxes, More settings, Set locale and Reset. Keep More settings’ lavender text and the existing blue checked/action states.
• Scope the styles to SERP and preserve the working Light / Dark / Match Google behavior, native selects, control sizes and menu positions. Use an outline or ring that does not change layout, and retain visible focus in light mode.

Files: src/components/serp/SerpControlPanel.tsx, src/components/serp/control/SerpParametersDropdown.tsx, src/components/serp/control/SerpLocalePanel.tsx, src/components/serp/control/LocaleSelect.tsx and src/assets/styles/serp.css. Keep shared button, dropdown and checkbox changes gated to SERP.

Screenshot · Locale focus, October 13

Original user-supplied capture, retained unchanged. Parameters, Export CSV, Country and Language require their own keyboard-focus checks.

Theme previews and earlier screenshots · October 12 reference

Google theme DarkLightSERP appearance Match GoogleLightDark

Historical chrome-2 sidebar markup, stylesheet, Inter fonts and SVG assets. Chrome-3 implements the dark theme; these earlier comparisons retain the approved appearance reference. Google’s dark page backdrop is #22242B. Proposed examples change theme styling only. Controls are local previews; they do not change extension preferences.

Expanded · overlay on

Expanded · overlay off

Collapsed · overlay on

Collapsed · overlay off

Locale expanded

Parameters open

Actual extension screenshots · October 12

Original supplied captures. Their scale differs from the native-size comparisons above.

• AuditItemHeader.tsx applies [&>svg]:-translate-y-[2px] to the check-label tooltip’s anchorClass. Only the SVG moves; preserve the label’s relative top-px, anchor and existing geometry.
• Keep all 8 Page Analysis, 2 Mobile Compliance and 16 Technical Compliance rows, label sizes/wrapping, 14 × 14px anchors/SVGs, 4px gap, status icons and tooltip behavior. No global Tooltip lift.

Files: src/components/shared/info/AuditItemHeader.tsx; caller src/components/report/panels/audit/AuditGroup.tsx. Release checks for zoom, wrapping and tooltip interactions remain separate from this implementation closeout.