Recent improvements

Per-regen quality score with auto-fix

Every regeneration now writes a parity report comparing what was scraped to what shipped — page coverage, content density, brand asset preservation, image use, plus a 0–100 score. Scores below 60 are flagged needs-review. When the legal-page generator fails, an amber banner appears with a one-click 'Fix legal pages automatically' button that retries just the legal step against the same row. No more silently GDPR-incomplete sites.

• ›Banner sits above the preview on the project page.
• ›Click the auto-fix button → privacy / terms / cookies / impressum / accessibility / 404 are restored without re-running the whole rebuild.

Your brand colour, not our default

The rebuild now snaps back to the brand's actual scraped primary colour when the design model drifts more than 45° of hue away. Red-branded sites stop coming out navy; orange-branded ones stop landing on green. Optional secondary and accent get re-derived against the corrected primary so the palette stays cohesive.

All product pages preserved

The planner used to lean toward 3–6 pages on every site, which destroyed value on product catalogs and portfolios. The rule is now source-shape aware: a 20-URL catalog produces ~18–22 pages, one per distinct product or category, not five collapsed into a /products index. Combined with a larger per-page image manifest, catalogs now ship with the product photography Google needs to rank them.

The system reads its own past mistakes

When a regeneration drops a page or skips a tracking integration, the warning is recorded with the specific URLs that went missing. The next regeneration's planner reads those warnings and is told 'do not repeat these omissions: /betoonkaev, /plastkaev, /komposiitkaev…'. Every chat-edit you make also gets logged, so the next full regen carries forward the corrections you've already applied.

Edit the global header and footer, not just sections

The AI editor used to handle page sections only; header and footer changes meant a developer. New 'Header (global)' and 'Footer (global)' options in the editor target picker — describe the change ('add a Pricing link', 'change the email to X') and the chat rewrites the chrome fragment for every page in one go. No per-page regen required.

Make-live workflow for drafts

Full regenerations now stay as drafts so a misfired regen can't silently overwrite your live site. Preview the new version in the dashboard; when you're happy, click 'Make live' on the version. Chat-edits and version restores still auto-promote — they're explicit user changes where what-you-clicked-is-what-you-want is the right default.

Google Search Console verification + LocalBusiness rich results

Project settings → Analytics now has a Google Search Console verification field. Paste the token from GSC's 'HTML tag' verification flow and the next save threads it into every generated page's head — verification survives regenerations. The LocalBusiness JSON-LD now also includes the required `image` property so Google's Local Knowledge Panel has a proper representative photo for your business, and every page emits a dedicated `<meta name='ai-description'>` for answer engines that look for it specifically.

No more frozen 'Generating…' badges

Background tabs throttle the polling timer that drives the dashboard's status badge, so a user who tabbed away during a regen used to come back to a frozen 'Generating…' label even after the site had finished. The page now refreshes the moment it becomes visible again — the status catches up to reality on the first tick. Selected version sticks across refreshes too: previewing v3 while v5 lands in the background no longer snaps you to v5.

Portfolio grid: card variant for mixed mockups

When the source site's portfolio has laptop / tablet / phone mockup PNGs of mismatched shapes, the new card variant wraps each image in a padded surface card with a permanent label below — absorbs the white frame mismatch into a uniform row instead of cropping device frames to aspect-4/3. The planner picks the right variant based on whether the source images are clean screenshots or device-frame mockups.