Job search
WordPress.com Review for a Job-Search Portfolio: Hosting, Plugins, and the Right Plan
Current paid-plan plugin access differs from old Business-only advice. Original requirements and dependency-handover exercises distinguish hosted portfolios, automated restoration, exports, and renewal consequences.
WordPress.com can host a job-search portfolio without a separate web-hosting purchase. Choose a plan by separating what the portfolio must show from how you need to maintain and recover it. Current plugin access is broader than many older comparisons suggest, while automated backups and developer tools still distinguish higher tiers.
This review checks public WordPress.com pricing and support guidance on October 21, 2026. It includes two completed fictional planning exercises, not an account, plugin installation, checkout, export, or recovery test. LandOffer publishes this review and offers job-search tools. Before choosing features, browse recent technical roles and identify the project evidence your intended reader needs.

Hosting is included; self-hosted WordPress is another arrangement
The WordPress.com versus WordPress.org guide explains the difference. WordPress.com supplies managed hosting around WordPress software. You do not need to buy a second hosting service simply to make that WordPress.com site accessible. A custom domain and paid third-party products can still create separate costs.
With self-hosted WordPress, you arrange hosting elsewhere and work within that provider’s environment. The software’s availability does not settle domain registration, server administration, update responsibilities, or assistance. Some hosts manage more of that work than others; self-hosting does not automatically mean running a server entirely alone.
For a job seeker, distinguish the website from the application you are demonstrating. A hosted project description can link to a separate software demo or repository. Paying for a more powerful WordPress plan does not establish that your Python service, database, or arbitrary application stack will run there. Identify which service will host the written case study, source repository, and working application before paying for features.
This is also different from purchasing a separate WordPress portfolio theme such as Semplice. This review evaluates WordPress.com hosting and plan entitlements; it does not verify compatibility with a particular external theme or replace that theme’s licensing and requirements checks.
Free, Personal, Premium, and Business solve different needs
The current pricing FAQ describes Free with a WordPress.com subdomain, 1 GB of storage, and unlimited pages and posts. It excludes custom-domain use, plugin installation, and ad-free visitor browsing. Free can support a content experiment if those limitations are acceptable; it is not equivalent to a paid custom-domain portfolio.
In the public annual-billing state we inspected, Personal displayed $4 per month, billed every 12 months, renewing at $5 per month. Premium displayed $8 and a $9 renewal basis; Business displayed $25 and a $28 renewal basis. Those are annual equivalents, not month-to-month charges. The monthly state showed Personal at $9, Premium at $18, and Business at $40, excluding taxes.
Personal’s annual figures imply $48 for the first 12 months and $60 for the next 12 at the displayed renewal basis. Local decimal arithmetic confirms those annual totals at the displayed basis; no checkout or account renewal quote was inspected. Premium adds items such as uploaded video and expanded statistics; Business adds automated backups/restores and developer access. Commerce concentrates on a store. A portfolio without sales does not, by itself, establish a need for Commerce.
Treat the current domain wording carefully. A free first-year domain badge remained visible on monthly cards, but the FAQ specifically says annual and multi-year plans qualify and monthly plans do not. Use that explicit qualification when budgeting, then confirm the actual offer before payment. Later domain renewal and existing registrar charges remain separate from the plan’s first-year headline.
Plugin access starts below Business, with compatibility limits
The current plugin support guide expressly permits installation on Personal, Premium, Business, and Commerce. Free is excluded. An old recommendation to buy Business merely to install any plugin is therefore a poor basis for today’s decision.
An installation entitlement is not a license to every paid plugin feature. Authors may offer free, paid, or mixed versions. Identify the specific feature, its license or subscription, its update terms, and whether it is already covered by the platform before adding another dependency.
There are also platform restrictions. The incompatible-plugins guide describes blocked or disabled products, including caching tools that overlap with managed hosting functionality. A plugin can also conflict with another active product despite not appearing on the prohibited list. We did not install anything or establish a particular combination’s compatibility.
Keep a small dependency list for a portfolio. Adding galleries, animation, analytics, and a page builder because each is available can make later changes harder to assess. Start by explaining what the reader must do, then decide whether a built-in page, an ordinary external link, or a plugin actually meets that requirement.
Worked plan decision: Mina’s portfolio feature audit
Mina is a fictional developer targeting roles that ask for clear project explanations and source-code evidence. Her planned site has Home, About, Resume, Contact, and three project pages. She has no store, membership offering, or requirement to host video files directly. Her software demonstration runs elsewhere; this is a proposed content architecture, not a deployed system.
She completes a feature audit before selecting a plan:
| Required reader task | Completed implementation decision | Plan implication |
|---|---|---|
| Understand her contribution to an inventory application | Write a project page with screenshots and a limitations paragraph | No plugin requirement identified |
| Inspect source code | Provide an ordinary repository link beside a static explanation | Do not buy developer-hosting tools solely for a link |
| Reach the live demonstration | Link to its separate host; keep a screenshot-based fallback | WordPress hosting does not replace the app host |
| View the resume | Provide a clearly labeled file link and keep an original local copy | Verify actual upload and visitor behavior later |
| Read under her own domain without platform ads | Select a paid plan; compare Personal first | Free fails these stated requirements |
| Recover an entire experimental site through built-in restoration | Mark this as optional, not required for her initial site | Business becomes relevant if this changes |
Her completed choice is to evaluate Personal, rather than Business, against these requirements. She selects no extra plugin at this planning stage. If a later essential plugin is compatible, Personal’s documented installation entitlement is relevant; the need for that plugin alone would not demonstrate that Business is necessary.
Mina’s written fallback for the separate demo reads: “This project is an independent inventory prototype. I implemented the import validation and interface shown here. The screenshots explain the main workflow if the live demonstration is unavailable; they do not establish production use or a measured business result.” It is finished sample portfolio copy for this fictional project, not a statement about a real candidate’s experience.
Her remaining acceptance tasks are specific: inspect the chosen theme on a phone, verify the resume download, follow the repository and demo links while signed out, and check the actual domain and renewal offer. None has been performed. Mina now has a plan to evaluate and a short acceptance list tied to the reader’s actual tasks; the portfolio itself remains unbuilt.

A content export is different from automated restoration
The dedicated backup guide places built-in automated backups on Business and Commerce, not Free, Personal, or Premium. It recommends content and media exports for the lower tiers. Broad statements about managed infrastructure should not be read as a promise that every plan provides the same owner-operated restore interface.
The export guide explains that a standard WordPress XML export contains written content and references to media, rather than the actual media files, themes, design customizations, and plugins. Separate media export and a complete backup or migration method serve different purposes. Calling an XML file a complete restorable website would hide those differences.
This matters even when the original content is modest. A custom layout, plugin-generated project grid, and external demonstration can each have a different preservation route. Keep the source text and original media you control, record the layout and dependencies, and identify what the destination will need before treating a migration as ready. This review did not generate, import, or restore an export.
Worked handover: Owen’s dependency and preservation record
Owen is a fictional designer with an existing hypothetical paid, plugin-enabled portfolio. He is considering ending the paid plan after a search. His site uses an external project-grid plugin, a third-party theme, ordinary project text, and original screenshots. No real site or subscription was inspected.
Owen’s completed handover record separates written stories, image files, plugin output, theme layout, and the resume route:
| Artifact or dependency | Preservation decision completed on paper | What it does not prove |
|---|---|---|
| Four written project stories | Identify a separate source document for each and list them for content export | No XML file has been generated or imported |
| Twelve original screenshots | Assign each to a project folder and require a separate media copy | References in XML are not twelve recovered files |
| Plugin-generated project index | Replace its dependency in the proposed handover with four ordinary project links | The actual grid has not been converted |
| Third-party theme and custom layout | Record a reference page map and choose a simple replacement layout | A content export does not retain that theme design |
| Resume PDF and contact route | Preserve the original PDF and a written contact line | No download or message delivery has been tested |
The proposed index is now concrete: “Project A — onboarding flow; Project B — scheduling study; Project C — reporting interface; Project D — accessibility review.” Each entry will point to an ordinary project page. These are fictional editorial labels, not verified links. Four ordinary links are his proposed replacement for the grid; he must still implement and inspect that route.
The cancellation guide gives Owen a reason to stop before removal: it says plugin content is removed when the paid plan is removed, and third-party themes are unsupported on Free. It also describes a return to the pre-plugin state and a private review state. Generic reassurance that posts and media remain should not be taken to mean every plugin-dependent presentation survives.
His completed decision is to defer removing the plan until he has exported content and media, rebuilt the proposed index, and inspected a replacement site. Those actions remain future work. He records the subscription owner and charge date as fields to confirm, rather than inventing them. The handover is a finished dependency decision, not a migration success report.
Review the charge date and choose the smallest justified plan
The automatic-renewal guide says yearly plans renew one month before expiration, while monthly plans renew on expiration. A reminder set only for the last day of an annual term can therefore be late for avoiding a charge. Discounts can also end before a later renewal.
The current refund guide describes 14-day purchase-or-renewal windows for annual and multi-year plans and seven days for monthly plans. Product types have separate rules. Canceling renewal alone does not issue a refund; immediate removal is a separate step with feature consequences. Check the actual charge and applicable terms rather than treating a refund headline as unlimited trial access.
WordPress.com is a reasonable candidate when included hosting and a maintainable publishing workflow meet your needs. Compare Personal first for a small custom-domain, ad-free portfolio; consider higher tiers when a required video, backup, or developer feature establishes the gap. Recheck current entitlements instead of importing an old plugin restriction or a self-hosted theme’s requirements.
Once the hosting decision supports the content, return to the job search: find recent openings on LandOffer and select the project that best explains your fit. Check that the intended visitor can reach and understand the work. This review establishes neither recruiter attention nor an employment outcome.
Sources and Further Reading
- WordPress.com pricing and current plan qualifications
- WordPress.com versus self-hosted WordPress
- Plugin eligibility and author pricing
- Incompatible plugins
- Automated backups and lower-plan export options
- What a content export includes
- Canceling versus removing a subscription
- Renewal timing
- Refund windows


