Before You Bulk-Import Word Documents: Back Up and Check Your Disk Space
A bulk import puts hundreds of posts and thousands of image files on your site in one afternoon. Two checks to do first: a full backup, and how much room the import has.
Is your site ready to go live? Real tests on speed, search, links, security and WordPress settings, with what was found and how to fix it.
We fetch your site's public pages to test them, the way a visitor would. Nothing on your site changes. We count the sites checked and their scores, never your IP.
Launch-day problems are rarely the big ones you planned for. They are the small settings left behind from building the site: a search-engine block that was right on staging, an address that still answers on both www and non-www, a contact page someone renamed, a plugin printing PHP warnings onto the homepage. Each one is a minute to fix and easy to miss, because the site looks fine to the person who built it.
The check runs about forty tests in six groups:
Most website checkers are happy to hand you a score. This one shows its working instead. Each result comes with the evidence it found: the status code a link returned, the header the server sent, the exact title it read. If something could not be tested, the report says it didn't run rather than filling the gap.
That matters when the report is going to someone else. A client, a manager or a developer you've hired can read the evidence and see the problem for themselves, without taking anyone's word for it.
Each result lands in one of four places:
"Discourage search engines" still ticked. WordPress has a checkbox under Settings, Reading that is meant for staging sites. It is easy to forget on launch day, and a site with it on can sit unindexed for weeks before anyone notices.
Two copies of the site. When both www and non-www addresses serve pages, search engines see duplicates and split the signals between them. One redirect fixes it.
Links that broke in the final edits. Pages get renamed in the last week before launch, and the menu or the homepage still points at the old address.
Errors shown to visitors. A plugin that throws a PHP warning prints it straight onto the page when debug display is on. Visitors see it before you do.
A user list anyone can read. WordPress's REST API lists author accounts and their username slugs, often the login name, unless something restricts it. That is half of what a password-guessing script needs.
It reads public pages, so it can't see inside your WordPress admin: plugin updates, backups and user roles are outside its view. It can't submit your forms either, so it lists them and leaves the test message to you. And a speed score is one run on one day, so treat it as a direction rather than a verdict; Google's real-visitor data, when your site has enough traffic, is the better long-term measure.
For the whole delivery, from the client brief through a block theme to a verified QA report and handover, the same checks run inside WPShipReady for Claude Code. The free check engine is also a command you can run on any site, including staging and localhost: npx wpshipready check yoursite.com.
That's your site checked.
This tool handles one document and gives you markup to paste. The DocxToWP plugin skips the copy and paste. It uploads your images to the Media Library as real attachments, fills your Yoast or Rank Math fields, and imports a hundred documents in one run.
The free plugin has no upload cap. Pro is from $49/year and adds bulk import, scheduling and SEO fields.
Yes. The summary of every check is free with no sign-up. The evidence behind each result, the step-by-step fixes and the downloadable report come with an email address, and that email only gets the report unless you tick the box for updates.
No. It tests the homepage in depth, follows every link on it to make sure each one answers, and reads site-wide files such as robots.txt and the sitemap. Most launch problems show up there first. It says so in the report rather than implying it read the whole site.
From Google's own Lighthouse, run through PageSpeed Insights on a phone and on a desktop, at the moment you press the button. If Google doesn't answer, the report says the speed test didn't run. It never shows an estimated score.
No. It only reads public pages and files, the same way a visitor or a search engine does. It sends nothing to your forms and logs in to nothing.
A count of the sites checked: the address, the scores, whether it's WordPress, your country and the time. Not your IP address. If you ask for the full report, your email is used to send it and nothing else, unless you tick the box for WPShipReady updates.
Yes. The general checks (speed, search, links, HTTPS, security headers, accessibility basics) work on any site. The WordPress section runs only when the site is WordPress, and says so when it isn't.
Not from this page: it only checks sites on the public internet. The same checks run on any address, including localhost, from the command line: npx wpshipready check followed by the address.
Nagz Studio, the people behind DocxToWP. The checks come from WPShipReady, a WordPress delivery toolkit for developers and agencies, and the free check engine is open source.
A bulk import puts hundreds of posts and thousands of image files on your site in one afternoon. Two checks to do first: a full backup, and how much room the import has.
Write the SEO title, meta description and URL slug at the top of your Word draft, and have them land in Yoast SEO or Rank Math when you import, instead of in the post. One document or a hundred.
Connecting an AI agent to WordPress can mean handing it the power to publish, edit and delete. Here is what to check before you connect one, and why a drafts-only connection is the safer start.