Edinburgh · Scotland
WooCommerce development in Edinburgh
A meaningful share of what reaches most stores is not people. Some of it is harmless, some is copying your prices, and some arrives all at once and takes the site down at the moment you most wanted it up.
Applied to all three, and felt by all three
- Brand A
- Brand B
- Brand C
Bots, scrapers and the traffic that is not customers
Automated traffic divides into three kinds and only one of them needs blocking outright.
Search crawlers are useful and should be allowed to work. Scrapers taking prices and stock are a commercial nuisance rather than a technical threat, and the honest position is that a determined one cannot be stopped — the aim is making it expensive enough not to bother, not building a wall. The third kind is the problem: bulk automated requests hitting the checkout, the login or the search, which consume the resources real customers need. The measures that work are unexciting. Rate limiting by address on the expensive routes, a challenge on the ones worth protecting rather than on every page, and caching aggressive enough that ordinary crawling costs you almost nothing. The mistake to avoid is over-blocking, because a rule tuned during an incident stays in place for years and quietly turns away real customers on shared connections, which produces no error anybody sees and no complaint anybody makes.
We have no office in Edinburgh. Our studio is in Rajkot, India, and every project here is delivered remotely — if a supplier who can attend your premises matters to you, that is a fair requirement and we do not meet it.
What a WooCommerce development project includes
Three things, and they are the same wherever you are. What changes is the subject above.
Custom themes and versioned business-logic plugins
Hosting architecture, caching and speed work
Migration, hardening and a named update policy
The other three, and what each one covers
Each answers a different question for Edinburgh businesses. None of them repeats this page.
AI Automation
Scoring risk without turning away real customers
Shopify Development
When there are fewer than there are buyers
UI/UX Design
One long checkout page, or four short ones
WooCommerce development questions from Edinburgh
Three questions about the subject above. How we work, what it costs and who owns the code are answered on the service page.
Can scrapers be stopped?
Not entirely, and a supplier who says otherwise is selling something. A determined scraper will get your prices. The realistic aim is making it expensive and slow enough to be not worth the effort, while keeping the site fast for the customers the measures might otherwise inconvenience.
Which routes actually need protecting?
The expensive ones: checkout, login, search and anything that queries the database hard. Protecting every page costs more than it saves and puts a challenge in front of ordinary customers, which is a measurable loss set against a threat that was never targeting those pages.
What is the risk of over-blocking?
A rule written during an incident and never revisited. It quietly refuses real customers on shared or mobile connections, produces no error anybody in the business sees, and generates no complaint because the person simply leaves. That is the most expensive kind of fault to carry.
Get in touch
Planning WooCommerce development work in Edinburgh?
Tell us what you are building and we will come back within one business day.
- Invoiced in
- GBP
- Office in Edinburgh
- None
- Reply time
- Within one business day