Product updates

Changelog

New features and improvements in AnswerLens.

A simpler recommendation chat

See the complete recommendation and discuss it in one focused screen.

September 7, 2026

The recommended actions stay visible above your conversation.
Open Review plan when you are ready to edit or approve; the chat stays uncluttered.

Discuss improvements before work starts

You can now ask questions, adapt recommendations to your business, and approve your own saved plan before a website preview is prepared.

September 5, 2026

Discuss alternatives such as using real testimonials when case studies are unavailable, with follow-up questions for missing material.
Conversations and edited plans are saved so you can return later.
Preparation starts only after explicit plan approval; opening a recommendation or review does not start work.
Preview preparation, exact-change approval, and developer publishing have distinct stages, and revisions invalidate earlier approval.

Website changes now run one clear task at a time

AnswerLens now prepares planned website work as a saved, sequential run that customers and developers can follow or return to later.

September 1, 2026

The run log names each task, affected file, generation attempt, validation result, plan review, and site-style review.
Long provider checks report that they are still active, and users can close the review window without stopping the work.
A missing review record is corrected without regenerating website files that already passed preparation.
Draft website work is prepared in the configured development repository instead of the live production repository.

Plans now become real page changes

AnswerLens can now create the new website files named in an approved plan and carry them into exact review.

August 31, 2026

New pages are shown with their complete proposed content before anything is sent to GitHub.
A separate safety sweep verifies that every proposed file satisfies the original plan and follows the website's existing style and theme.
Approval now records that the exact preview was reviewed and that a qualified developer must test the pull request before deployment.
The wizard continues automatically from a ready plan into exact file preparation.
Plan, preview, failure, and pull-request states now use distinct labels so a stopped change is never presented as complete.
Generated-work history can be cleared without deleting visibility checks or website code.

Website improvements now follow the wizard

The site page now keeps checking, choosing, reviewing, applying, and verifying in one clear numbered flow.

August 26, 2026

The improvement wizard now appears immediately below the site name instead of below separate dashboards and setup panels.
A completed visibility check leads directly to the latest result and recommended fixes.
Every recommendation now has a clear Choose this fix action that prepares the exact proposal for the next step.
Connections, security tools, detailed analysis, and technical records stay collapsed until they are needed.

Repository rebuilds no longer repeat the same failure

A rebuilt website change can now move to exact review when its remaining checks must run on the published site.

August 23, 2026

Live-site acceptance checks remain pending until deployment instead of blocking a complete source change.
Rebuilt image accessibility work can proceed to before-and-after review without returning to the same repository warning.
Repository rebuilds now refresh when either the linked code revision or rendered image audit has changed.
Image accessibility rebuilds now review every matching source file, including large application pages, and offer a fresh rebuild when verification finds anything outside the saved scope.

Website improvements now follow one clear path

Each recommendation now moves through six numbered steps, from checking the website to reviewing exactly what changed.

August 6, 2026

A single next-step card guides you through choosing, reviewing, applying, and verifying one improvement at a time.
AnswerLens shows the exact files and before-and-after content before you approve a GitHub pull request.
History keeps each numbered fix, its source, changed pages, GitHub result, live verification, and undo guidance together.
Stopped changes now say clearly that the website was not changed, with technical details available only when needed.

Repository fixes are easier to trust and review

Connected repositories now stay in sync across scanning and patch review, with one clear next change to review at a time.

August 4, 2026

The security scan recognizes a repository as soon as it is linked and keeps that state after a reload.
The Action plan separates recommendations from generated work and shows one clear review path without selection or sharing controls.
Rebuilding from the linked repository replaces the stale failed item, and valid edits no longer stop because the provider omitted redundant evidence.

Deep analysis stays available

Completed deep analysis now remains available when you return to a site or refresh the page.

July 10, 2026

The signed-in desktop menu stays visible at large screen sizes instead of opening as a full overlay.
Deep analysis results are saved after they run and reload automatically on the site page.
Analysis results remain readable in light mode, dark mode, desktop, and mobile layouts.

One consistent look across AnswerLens

Every AnswerLens page now carries the same violet-led visual theme as the home page.

July 10, 2026

Primary actions now use the same violet treatment across public pages, account workflows, reports, and error states.
Shared light and dark backgrounds, cards, focus states, and page headings now feel consistent throughout the product.
Navigation now keeps public links separate from signed-in product links and clearly marks the current page.

Business profiles that fit the real business

New sites can now explain their full offering instead of choosing a single category or location.

July 10, 2026

A large business-description field captures services, customers, specialties, and differentiators in the owner's own words.
AnswerLens composes that explanation into a clear profile for AI agents and more relevant starter questions.
Service area is no longer required, and online businesses receive starter questions without forced local wording.

Clearer service health and support

AnswerLens now makes service availability easier to understand and gives customers a direct support path when something goes wrong.

July 10, 2026

A public status page shows application, data storage, scheduled monitoring, and engine configuration readiness.
Customers can report an issue from any page without leaving their current workflow.
Unexpected failures are recorded for support triage with sensitive values redacted.
After an AnswerLens deployment, stale pages now offer a clear automatic refresh path.

A more accessible AnswerLens

AnswerLens is easier to navigate with a keyboard, screen reader, or accessibility display preferences.

July 10, 2026

Clear keyboard focus indicators and a skip-to-content link make navigation faster.
Forms, dialogs, and status updates now provide more useful labels and announcements.
Reduced-motion, high-contrast, and forced-color preferences receive better support.