Skip to content
Alex’s AI Websites
A bookbinding workbench with a brass press, leather, and hand tools.
Hands working carefully on a leather-bound book at a dark workbench.
A bookbinder shaping and finishing a precise piece of leather.
One finished oxblood leather book with gold detailing.
A stack of finished leather books with gold spine rules.
PRODUCTSOLUTIONSPRICINGPROOFCONTACT

Prompt to done

Ask for the website change. Review the finished result.

Turn a positioning update, product story, or campaign idea into a working website change without managing another chain of handoffs.

Routine changes

Keep the website moving with the team.

After the rebuild, routine edits can be made without waiting for a designer or developer every time.

Documented speed

Small changes can happen in minutes.

Documented examples include a site-wide word change in one pass and new industry pages drafted in minutes.

Automatic wiring

The parts around the page come with it.

New work stays connected to the shared navigation, forms, analytics, and reusable page system instead of becoming another isolated page.

SEO and AEO checks

Check the page before it ships.

Automatic checks cover the technical details that help search engines and AI assistants discover, read, and understand the website.

Scroll

The service

From prompt to a finished website change.

Tell me what needs to change. I turn it into a working update, keep the surrounding navigation, forms, analytics, and page system connected, then run the SEO and AEO checks before it ships.

See how the service works →

Proof

A 24+ page rebuild, with more than 10 homepage versions to review.

About two weeksfrom rebuild start to a review-ready website

One implementation ownerfrom page system through launch checks

Secuvy.aithe full rebuild behind the proof

See the Secuvy proof →

Common questions

What changes after the rebuild?

Is alexau.net optimized for SEO and AEO?

It is set up for SEO and AI assistants with open robots, a curated llms.txt, schema markup, and the AI grading CTA on the Proof page. This does not claim search rankings.

How fast can I change my site?

Routine changes typically move in 1–2 days after launch. Documented examples include a site-wide word change in one pass and new industry pages drafted in minutes.

Do I need a designer or developer for changes?

Routine edits can be made by the team without a developer after the rebuild.

A useful first step

Send me your site.

Tell me what is stuck. I’ll review it and reply in 1 business day with what I think is causing the delay, what looks possible, and whether I can help. No call required.

Best fit: B2B companies actively changing their positioning, products, pages, or acquisition strategy.

By submitting, you agree that I can use these details to respond to your enquiry. See the Privacy Policy.