Skip to content
←︎ MEET MAXENGINEERING NOTES / MW CODES

FOR DEVELOPERS, AGENCIES AND THE CURIOUS

A change isn’t done
when it’s saved.
It’s done when it’s there.

Max finds website problems, prepares specific improvements and checks that they reach the live page. Every step leaves evidence. Even when the answer is “that didn’t work”.

Talk through your setup
THE STANDARD FOR EVERY CHANGEMAX / FIELD NOTES

01 Locked to the version it was based on.

02 Confirmed in the page a visitor receives.

03 Recorded, restorable, measured.

EVIDENCE
BEFORE CREDIT

01 / FOLLOW A CHANGE

A complete loop.
Every step earns the next.

Choose a stage to look inside the process. This is how a finding becomes a checked result.

PROCESS NOTESSTAGE 01 / 09

Start with the evidence.

Build an inventory of missing metadata, thin content, broken links and pages that are difficult to discover.

OUTPUTA prioritised list of findings

02 / TWO DIFFERENT CLAIMS

The CMS said yes.
The page said otherwise.

A plugin can override metadata. A cache can keep serving yesterday’s page. A clean deployment can still miss the intended change.

Max treats the write and the result separately. Only the live output can confirm completion.

ILLUSTRATIVE VERIFICATION RECORD

Write accepted
Yes
Live page fetched
Yes
New title visible
No
RESULTNot verified.

Keep the reason. Do not count it as done.

03 / MEASUREMENT WITHOUT THE VICTORY LAP

Sometimes the most
useful result is
“we can’t tell yet”.

Search and analytics results are compared with a baseline and the page’s normal variation. Low-volume pages need extra care because a handful of visits can look like a large percentage gain. Newly connected sources keep their own baseline, so adding Search Console does not manufacture an improvement. Max can report no measurable difference or insufficient evidence; every change is not labelled a win.

  • Use the page’s own baseline.
  • Account for normal variation.
  • Keep newly connected sources separate.
  • Be more cautious with low traffic.

No measurable difference is a valid outcome.

03 / A COLLEAGUE WITH GROUND RULES

He’s got initiative.
We’ve got the final say.

Every website is different. We agree what Max can take on and keep the important decisions with our team.

A NOTE FROM THE TEAM

Show us first.

Max prepares the change and explains it. Our team reviews the proposal before anything is published.

The starting point for every website.
MWReviewed by people.
Looked after by us.

05 / DIFFERENT PLATFORMS. THE SAME DISCIPLINE.

A CMS and a repository
need different routes.

ROUTE 01

WordPress

A connector runs on the website and accepts the declared operations through a signed channel. Max does not use an administrator password or click through the admin interface. Writes are locked to the version read and checked against the live page afterwards. The connection is an integration we set up, rather than permission for an assistant to browse your whole account.

Signed connector →︎ version-locked write →︎ live check
ROUTE 02

Built from code

Max reads through a signed, read-only endpoint and prepares changes on its own branch. The hosting platform builds a preview; that preview is checked before production, and production is checked again afterwards. Editable fields and areas are explicitly declared and reviewed. Max does not infer ownership of a shared component from finding its text on a page.

Branch →︎ built preview →︎ production →︎ live check

06 / THE BOUNDARIES ARE PART OF THE PRODUCT

Good judgement includes
knowing where to stop.

Confirmed facts only.

Prices, phone numbers, qualifications and guarantees come from confirmed information. Max is not allowed to fill those gaps with a guess.

Declared editing areas.

Shared navigation and common components need explicit permission. A finding on one page does not grant ownership of every place its words appear.

No running project code.

Max reads repositories and prepares commits. He does not execute install scripts, hooks or project code to understand a site.

People choose updates.

Outdated software is flagged for attention. Dependency changes are a team decision, with checks afterwards.

Stop if the page moved.

If somebody edited the content after the proposal, the stale write is refused. Later changes can also require a person to handle restoration.

Keep the relationship.

For agencies, Max works behind your team. You decide how to introduce him. Your clients and the relationship stay yours.

BEFORE WE SAY HELLO

Good questions.
Proper answers.

Does every published change improve traffic?

No. Normal variation, seasonality and limited data can prevent a reliable conclusion. The measurement is allowed to say that there is no measurable difference or not enough evidence.

Can I keep human approval for everything?

Yes. Proposals can continue to require approval. More autonomy is not a requirement of using Max.

What if a cache hides the change?

The saved value and the live output are treated separately. If Max cannot verify the intended output, the change is not counted as successfully applied.

Does Max install dependencies?

No. He can flag outdated software, but a person decides on dependency changes. He does not run project code or install scripts to understand a repository.

What should an agency send first?

Your website platforms, approximate portfolio size and the work you want help with. We will discuss integration requirements and how Max would fit your review process.

LET’S MAKE SOMETHING USEFUL

Your next chapter.
Starts with a hello.

A new website, a better one, or just a question.
Tell us what’s on your mind.

Message us on WhatsApp
01905 917333 WhatsApp only