Editorial Policy

Blogger Novawrites about WordPress hosting itself - choosing a host, buying it, setting it up, making it fast, securing it, and fixing it. We cover each host's plans and pricing, the real speed and uptime we measure, the resource limits that decide what your site can handle, renewal costs and add-on fees, WooCommerce and use-case hosting, and how to migrate, optimize, and troubleshoot a WordPress site. We do not cover the host-provider side of the business, generic domain reselling, non-WordPress platforms, web design services, or non-US hosting law.

Our editorial calendar is built from public search demand (which questions US WordPress site owners actually ask), gaps in existing coverage, and our editors' direct experience signing up for, testing, and date-stamping hosting plans. The editor-in-chief approves every topic before drafting begins; the category-owning editor writes the draft; a designated fact-checker (usually the host-testing editor) re-checks each claim against an account we pay for and our own measurements; a senior editor signs off before publication.

• We do not accept payment to publish a favorable write-up of a host's plans or performance.
• We do not accept payment to change the ranking, scoring, or recommendation of a host after we've tested it.
• We are not owned by, partnered with, or financially related to any hosting company, infrastructure provider, or platform.
• Our revenue comes from (a) affiliate commissions on hosting signups made through links on our site, (b) display advertising sold on a programmatic basis, and (c) occasional clearly-labeled sponsorships (see Sponsorship Policy below).

Affiliate Disclosure

Blogger Nova earns affiliate commissions when you click a hosting link on our site and sign up. These commissions are our primary revenue, but they do not influence which hosts we choose to cover, how we rate or rank a host, or how prominently a host appears in our comparisons. Host selection is determined by editorial relevance and reader demand; rankings are determined by our own test results and editorial judgment. No affiliate partner receives preferential placement, and we will rank a faster, better-value host with no affiliate link above a worse host that carries one.

Sponsorship Policy

From time to time, Blogger Nova publishes sponsored content - articles, videos, or other media funded by a brand partner. Every piece of sponsored content is:

• Clearly labeledwith a “Sponsored” or “Paid Partnership” tag visible before the reader begins consuming the content.
• Editorially controlled - the sponsor may suggest a topic but may not approve, alter, or veto the final copy.
• Separated from our review verdicts - sponsored content never takes the form of a host review verdict or appears inside a best-and-worst ranking.

Review Sourcing Policy

Every host review we publish is based directly on an account we pay for ourselves and our own measurements - their published plans, pricing docs, or our benchmark runs - never from a sponsor, a vendor contact, or a forum thread. We never let a host dictate, edit, or approve how we describe its performance, and no hosting company is given advance review or exclusivity. Regardless of which host it covers, every review goes through the same standardized testing and date-stamping process.

Every editor and contributor is required to disclose personal conflicts of interest to the editor-in-chief. A conflict includes, but is not limited to: a financial interest (stock, consulting fees, sponsorship) in a company whose hosting we cover; a personal or family relationship with an employee of such a company; or any prior or pending employment relationship with a hosting company, infrastructure provider, or platform in our coverage area. Disclosed conflicts are evaluated by the editor-in-chief, and the individual is recused from relevant coverage when warranted. If an editor departs Blogger Nova to join a company we cover, all articles they authored are re-reviewed by a remaining senior editor within 90 days.

Every factual claim about a specific host's plans or performance must trace to either (1) the host's own published plans and pricing (pricing page, docs, or dashboard), (2) a test we performed and date-stamped on an account we pay for, or (3) a named authoritative source we explicitly trust (e.g., an official status page, a published SLA, or independent uptime monitoring). We do not cite forum posts as a source; we may quote a forum post for color, but the underlying claim must be independently verifiable against our own testing.

Every article carries the byline of a real editor on our team. Where required, every article also carries the name of the reviewer who signed off. We do not publish unattributed articles.

Our Position on AI

We do not use AI to generate article body copy. AI-assisted tooling (grammar checks, transcript clean-up, headline brainstorms) is used by our writers as a working aid only, and the final writing is theirs.

Where AI tooling is used in our research or testing pipeline - for example, monitoring a host's pricing page for changes or structured comparison generation - the underlying data still originates from our hands-on testing on accounts we pay for, and every AI-assisted output is reviewed and validated by a human editor before it informs published content. We will update this section as our tooling evolves so readers always know what role AI plays in our workflow.

Articles older than 18 months are flagged for review. Host reviews are re-tested on accounts we pay for on a regular cadence and re-stamped with a fresh “Last tested” date. Best-and-worst comparisons are refreshed at least once per calendar year. We never silently backdate an updated article - the “Last updated” timestamp is honest.

Mid-Cycle Updates

When a significant event affects a host between scheduled re-tests - a renewal-price hike, a new or changed resource limit, a switch to slower hardware, or a major plan change - we update the relevant article within 14 business days and note the change with a dated inline update tag.

We post every correction publicly to /about/corrections/ and update the article inline with a “Correction (date): [what changed and why]” note. Reader-reported corrections are taken seriously; contact us is monitored by the editor-in-chief.

If a correction materially changes a host recommendation or a review verdict, we re-notify readers who engaged with the original article through on-site update banners and, where possible, email alerts.