WordPress web development services, for an exporter, are a scope and a handover. A theme demo is neither. The useful question on the last day is what you can still change when the developer is no longer in the project chat. If the answer is “mail them”, the project did not end. It paused, with you locked out of your own admin.
This page is that ending, written forwards. What belongs in the scope. What the handover must contain. How to judge a bundled host, including the search people type as godaddy for wordpress, without turning the judgment into a signup guide. And what we will not put in the scope even if a brief asks for it.
Scope is a list of URLs and jobs
Write the URLs, or write a cap and a change order. “A modern catalogue” is not a scope. A scope says which product types get a template, which languages get a real URL, which form fields exist, and which integrations are in or out. Payment, stock sync, a dealer login, a second brand. Each one is a different size of job. Bundling them into a single adjective is how the argument starts in month three.
Separate content entry from the build. Designing a product template is one job. Typing 400 SKUs into it is another, and it is often larger. If your staff will enter the data, say so, and budget a training session with a clock on it. If the studio will enter the data, they need a real sheet, not a promise that the sheet is “basically ready”.
Name the host as in scope or out of scope. A build that assumes unlimited PHP memory will fall over on a small machine. One recorded case was a 1-core, 1 GB server running three WordPress sites, with memory_limit set to 1024M. A single PHP process used 80–124 MB. The stable setting was 256M, with workers cut from 6 to 4. Any WordPress web development services agreement should say who checks that arithmetic before launch, because a beautiful template on a mis-set ini file still times out for the buyer.
Handover is access, not a PDF
On the last day these objects change hands.
- An administrator login on an email your company controls. The studio’s extra admin accounts removed or reduced.
- The host login, the DNS login, and the registrar login, each with its own password store. One shared spreadsheet titled “passwords final” is how the next person gets locked out.
- Where mail is hosted, because it is often not the web host. A website launch that also hijacks the sales inbox is a failed handover even if the theme looks right.
- A form test, already completed, from a phone on a network outside the studio, with the message visible in the destination inbox.
- The live PHP memory_limit, the worker cap, and whether a page cache exists. Written down. Not “performance has been optimised”.
- A scan note for public leftovers. One site had 36 .backup files inside the theme, downloadable by anyone. The handover should say the web root was checked, and what was removed.
A PDF that repeats the sales proposal is not on this list. You may want the PDF for your own files. It does not operate the site. Access operates the site.
Can your own staff change a phone number, a price, and a product photo without writing to the studio? Sit with them and watch. If they cannot, the training session has not happened, whatever the calendar says. Do this before the final invoice, while there is still a reason for someone to fix the rough edge.
Godaddy for WordPress, judged as a constraint
People search godaddy for wordpress when a domain, a mailbox, and a one-click WordPress install already live in one bill, and someone has asked whether that bundle can carry an export catalogue. This page will not walk through an account signup. Signup guides are a different product, and they go stale on the vendor’s next redesign.
Judge the bundle, or any other bundled host, with the same questions you would ask a VPS. What is the live memory_limit, and what is the RAM behind it. Can you read the PHP error log. Can you set a page cache, or is that file locked. Can you leave with a copy of the files and the database, in a format another host will accept. Who answers when the form stops sending on a local holiday.
A managed install that hides those answers can still be the right place for a small brochure, if a named person at the host will do the checks you cannot. It is a poor place for a catalogue the moment you need to see why PHP died. “Godaddy for wordpress” is then not a brand decision. It is a visibility decision. If the panel will not show you the ini value, you cannot run the arithmetic that kept the 1 GB machine upright.
Leaving that bundle later is a migration, with the plugin caveats that implies. Plan the exit while the site is small. Know where the domain is registered, separate from where the site is hosted, so a host dispute cannot hold the name. That separation is ordinary professional hygiene. It is also the difference between a weekend move and a week of waiting on a ticket.
What does not belong in the scope
A guarantee of rankings does not belong there. Google’s published position is that no one can guarantee a number-one ranking, and that a special relationship with Google is a claim to walk away from. The page is Google’s note on hiring for search. WordPress web development services can build a page a search engine can read. They cannot sell the position.
A hundred near-duplicate city pages do not belong there either. If the brief asks for them, the brief is asking for a clean-up. Say so. A real location, with a real person, is a different request and can be scoped as one URL.
A promise of a fixed enquiry count does not belong there. The form can be built and tested. The count of people who use it depends on demand, on the offer, and on whether anyone answers. We can test the first. We will not invent the third as a target.
An acceptance hour, with your own staff
Block one hour before the final invoice. Your staff, not the studio, performs the hour. Change a phone number and change it back. Replace one product photo. Submit the form from a phone on a mobile network. Open the host panel far enough to see disk space. Find the document that says where mail is hosted.
If any step needs the developer in the chair, the handover is incomplete. Note which step. Fix that step. Repeat only that step. A second full demo from the studio does not count. The point is that someone who will still be here in November can operate October’s site.
Write the result in four lines. Who sat the hour. Which steps passed. Which step failed. The date of the retest. That note is the acceptance record. A smile in a meeting is not.
Add the theme’s name and the page builder’s name to the same note, in words a later supplier can search. “Custom WordPress” is not a name. A widely used theme with a public changelog is a name. If the build sits on a private child theme, the handover includes that child theme’s files and a sentence on what the child changes. Without the sentence, the next person edits the parent and loses the change on the next update. This is ordinary WordPress web development services work, and it is the part that gets skipped when the demo looked finished.
The thirty days after
The first month is when the missed object appears. A product sheet nobody entered. A form notification going to a freelancer who has left. A plugin update the host applied, which reset a setting. WordPress web development services should name who watches that month. If it is a separate support retainer, say so in the scope, with a start date. If it is included, say how many hours, and what happens to a request that is actually a new feature.
Did your staff complete the acceptance hour without the developer driving? If the answer is no, you are not done, whatever the calendar invite said. Hold the last payment to that hour if you still can. It is the cheapest leverage left in the project, and it is legitimate, because the hour is the handover.
Keep a single place for the logins. A password manager with two people in the company, not one. A bus factor of one on the registrar password is how a domain expires during a holiday. The developer should not be one of those two people after the project ends, unless a written retainer says they are.
Where this sits next to other work
The service line for the build is WordPress development. The line for the months after is WordPress support. Search, when it is actually in scope, is technical and multilingual SEO, with its own definition of done. Keep those contracts separate even if one studio holds all three. A single blended retainer is how a broken form gets billed as “SEO” and nobody opens the inbox.
Tianwen Network was founded in 2017. Liu Yu is the technical lead. The studio maintains 30–40 export WordPress sites, and three of its own. The memory figures and the backup-file count on this page come from that maintenance. They are checks for your handover, not a story about an unnamed client’s growth.
If you have a scope draft, send it. The useful markup is which lines name an object, and which lines name a hope. The contact page takes the long version. A shorter one fits on WhatsApp: message Tianwen on WhatsApp. Attach the URL list, or say you don’t have one yet. Both are workable. A ranking guarantee is not.
Questions about scope and handover
What has to be true on the last day of a build?
Your company holds an administrator login, the host and DNS logins, a form test that reached a real inbox, and a written memory_limit. A PDF of the proposal is not a handover.
How should a GoDaddy WordPress bundle be judged?
By whether you can see memory_limit, the error log, the cache layer, and a way to leave with the files and the database. The search phrase godaddy for wordpress is a constraint question, not a signup guide.
Should the scope promise a ranking?
No. Development can build a page a crawler can read. Google’s own note says no one can guarantee first place. Keep that sentence out of the contract.
Who should pass the acceptance hour?
Your staff, without the developer driving. Change a phone number, replace one photo, send the form from a phone, and find where mail is hosted. If a step needs the studio, that step is not done.