Reproduce first, then change
We ask for the exact URL, steps, error message and recent change so the fault can be reproduced before editing production code.
WORDPRESS SUPPORT / PERTH, WA
One-off technical help for WordPress sites that are broken, stuck or need a defined change. We diagnose the fault before prescribing a rebuild: plugin conflicts, PHP errors, form failures, WooCommerce issues, theme problems, content changes and scoped functionality can all be handled without forcing a monthly retainer.
reproduce the issue before changing codebackup the affected site where possiblefix the cause, not only the visible symptomverify the exact customer path after repair REPAIR BEFORE REBUILD
Support starts by identifying the smallest safe change that solves the issue. A broken form does not automatically need a new website, and a plugin conflict should not become a redesign project unless the existing foundation makes repair genuinely uneconomical.
We ask for the exact URL, steps, error message and recent change so the fault can be reproduced before editing production code.
A broken layout may come from CSS, a builder update, missing assets, cache or a PHP error. Diagnosis identifies which layer actually failed before work is estimated.
Where access allows, we create a backup and use staging for risky changes. Small low-risk edits can be handled directly when a staged workflow would add more risk than value.
After the fix, we repeat the steps that exposed the issue: submit the form, add the product, complete the handoff, open the mobile menu or load the affected template.
DIAGNOSIS BEFORE BILLABLE GUESSING
One-off support is for a defined problem or small queue of changes. We work from evidence: symptoms, logs, recent updates, browser console, PHP errors, plugin/theme state and hosting constraints.
Recover access, identify the failing plugin, theme or custom code path, inspect relevant logs and restore a stable state before making the permanent fix.
Check the form event, validation, WordPress mail path and configured destination before blaming email. DNS or mailbox delivery issues are identified separately from a WordPress form fault.
Repair CSS, JavaScript, template or builder regressions that appear after updates or edits without converting a focused layout issue into a full redesign.
Resolve administrator access, capability, redirect-loop and common authentication problems where the account and hosting ownership can be verified.
UPDATES OFTEN EXPOSE OLD ASSUMPTIONS
Plugins and themes fail for different reasons: version incompatibility, deprecated PHP, JavaScript collisions, database changes, licences, abandoned vendors or custom overrides. We isolate the dependency before replacing anything.
A STORE PROBLEM IS OFTEN MORE THAN A PAGE PROBLEM
WooCommerce support follows the transaction: product data, cart, checkout, payment, shipping, tax, order creation and customer email. The fault can sit in WordPress, an extension or an external payment/shipping service.
Repair price, stock, attribute, variation or product-template problems that stop a customer selecting the item correctly.
Diagnose cart fragments, coupons, quantity rules, session issues and plugin conflicts affecting the pre-checkout path.
Separate WooCommerce configuration faults from Stripe, PayPal or other gateway-side failures using logs and test mode where available.
Review shipping zones, classes and extension behaviour when customers receive the wrong rate or no available method.
Check whether the order record, status transition and agreed transactional emails are created after checkout.
Trace failures in external syncs or webhooks when the store is healthy but downstream systems stop receiving data.
SUPPORT IS ALSO FOR THE SMALL CHANGES THAT BLOCK MARKETING
Not every support request is a fault. Existing sites often need a controlled change: a new lead form, CTA, landing-page section, tracking event, staff profile, downloadable resource or small business rule.
ERROR MESSAGES ARE CLUES, NOT THE DIAGNOSIS
A durable fix needs evidence from the right layer. We combine browser errors, PHP logs, WordPress debug information, version history, plugin/theme state and hosting constraints to narrow the fault before changing code.
Most support can be delivered remotely across Perth CBD, West Perth, Subiaco, Osborne Park, Joondalup, Fremantle, Cannington, Midland, Wanneroo and Rockingham. What matters is secure access to WordPress, hosting and the failing workflow—not whether the developer is physically beside the server.
Front-end JavaScript failures, blocked assets, CORS problems and failed requests are traced before altering PHP or replacing plugins.
Fatal errors, memory exhaustion, deprecated functions and repeated warnings are matched to the component and action that triggers them.
The current WordPress, PHP, theme and plugin versions are checked for obvious unsupported combinations before a workaround is accepted.
Updates, migrations, DNS changes, new code and content edits are ordered by time to reduce the search space around when the failure started.
Page caches, object caches and CDN behaviour are cleared or bypassed in diagnosis so stale content is not mistaken for a code failure.
The repair is tested using the same steps, device state or customer action that originally exposed the problem.
WHEN THE SITE IS DOWN, RECOVERY COMES BEFORE BEAUTY
Emergency work prioritises stabilisation: regain access, preserve evidence where possible, restore the customer-facing path and only then perform the deeper repair. Security incidents may move into the dedicated Security & Recovery service when forensic cleanup is required.
Confirm whether the site is completely down, partially broken, hacked, checkout-blocked or only affecting one admin workflow.
Severity + affected customer pathTake a backup or snapshot where possible before making rescue changes, unless the host or compromised state makes that unsafe.
Recovery point / evidence preservedUse rollback, plugin isolation, theme fallback or a known clean restore to bring the critical public path back where possible.
Stable customer-facing stateTrace the component, update, custom code or infrastructure condition that created the failure rather than leaving the temporary workaround in place.
Cause documentedPatch, replace, reconfigure or escalate the failing component and re-test the original failure path.
Verified fixDocument the update, maintenance, hosting, security or architecture change that would reduce the chance of the same incident returning.
Next-risk recommendationONE-OFF SUPPORT WITHOUT A RETAINER
Use hourly support for a small defined issue or pre-purchase a block when you have a short queue of repairs and changes. Time is used for diagnosis, implementation, testing and notes—not only keyboard time. Larger redesign, migration, security or development projects are quoted separately once the issue crosses into project work.
Published Perth WordPress support examples currently advertise one-off support around A$99/hour, while broader Perth technical support is advertised around A$180/hour ex GST. Alpha's one-off WordPress support starts at A$72/hour, matching the guide rate already shown on the Services page.For a specific WordPress fault, small repair or clearly defined change where an ongoing plan is unnecessary.
1-hour minimum · then 30-minute incrementsFor several related fixes, content changes or a problem that needs diagnosis plus implementation and testing.
4 technical hours · use within 30 daysFor a larger queue, WooCommerce investigation, compatibility cleanup or multiple issues across one existing WordPress site.
8 technical hours · use within 60 daysGuide prices are in AUD. Third-party licences, hosting, paid APIs, premium plugins, vendor charges and external provider fees are excluded. Out-of-hours emergency work is not included in the A$72/hour standard rate and is quoted before work starts. Confirmed malware cleanup, forensic recovery and broad redesign/migration work move into the appropriate dedicated service. GST treatment is confirmed in the final proposal.
Standard approved WordPress support: A$72/hrYOU SHOULD KNOW WHAT HAPPENED TO THE HOURS
Support is easier to buy when the process is visible. Each request starts with the failing URL or desired change, records what was reproduced, and ends with the fix or a clear next scope if the issue is larger than support.
Prefer Ongoing Care? →Send the issue with the URL, screenshots or error text, recent changes and access needed. We keep related work grouped so diagnosis is not repeated.
If a one-hour repair turns out to need a migration, security cleanup or custom-development project, we stop and explain the new scope before consuming more time.
Diagnosis, code changes, testing and technical notes count as support work. Third-party waiting time or vendor charges are not disguised as development.
Material repairs include a short record of the cause and change so a future developer is not forced to rediscover the same fault.
SUPPORT QUESTIONS BEFORE YOU BOOK TIME
These answers explain how one-off WordPress support is priced, what can normally be repaired without a rebuild and when a support request should become a larger project.
Our standard one-off rate is A$72/hour with a one-hour minimum, then 30-minute increments. We also offer 4 technical hours for A$288 and 8 technical hours for A$576 when you already have a short queue of issues or changes.
Often, yes. We first reproduce the issue and identify the failing layer. A plugin conflict, broken form, PHP error or layout regression can usually be repaired independently. We recommend a rebuild only when the existing foundation makes a safe repair uneconomical or temporary.
Standard support targets an initial response within 1–2 business days, with priority blocks targeted for the next business day. The repair time itself depends on whether the fault is reproducible, access is available and a third-party vendor or host is involved.
Yes, subject to availability, but out-of-hours emergency work is quoted separately and is not included in the A$72/hour standard rate. A hacked site may also require the dedicated Security & Recovery scope rather than normal troubleshooting.
Yes. We isolate the conflicting component, check WordPress and PHP compatibility, inspect custom overrides and then recommend configuration, patching, replacement or vendor escalation based on the actual cause.
Yes. Support can cover product and variation issues, cart or checkout problems, shipping rules, payment configuration and order-flow faults. Large store rebuilds, migrations or new custom commerce features are scoped separately.
Yes. Small form, layout, CTA, tracking, content and feature changes can use support time when they fit the existing design and codebase. New custom systems or multi-page redesign work is better handled as a development or redesign project.
No. One-off support is specifically for businesses that need a defined repair or change without a retainer. If the same site needs recurring updates, backups and monitoring, the separate WordPress Maintenance service is usually more economical.
It depends on the problem. WordPress admin is usually the starting point; hosting, SFTP/SSH, database, DNS, payment-gateway or analytics access may be needed for deeper faults. We ask only for the access relevant to the issue.
Support is delivered remotely across Perth metro, including Perth CBD, West Perth, Subiaco, Osborne Park, Joondalup, Fremantle, Cannington, Midland, Wanneroo and Rockingham, as well as WordPress sites elsewhere in Australia.
SEND THE SYMPTOM AND THE URL
Show us exactly what is broken or what needs changing.
Send the affected URL, what you expected to happen, what happened instead, any error message, and the most recent update or change you remember. We will tell you whether it is a one-off support job or a larger project before unnecessary work starts.