Wikipedia protects a page in one of five ways, and each one names its own key. No protection lets any registered account edit directly. Semi-protection raises the bar to autoconfirmed status: an account at least four days old with at least ten edits behind it. Extended-confirmed protection multiplies both numbers — thirty days, five hundred edits — and full protection removes the option for anyone who isn't an administrator. A fifth setting, pending changes, lets an edit go through the motions of being saved while holding it out of the version readers actually see until someone with standing approves it.
Most protected pages sit at the first working level. Semi-protection is the routine answer to a routine problem — an IP address blanking a paragraph, a rotating cast of throwaway accounts restoring the same unsourced line — and it lifts on its own the moment an account clears four days and ten edits doing almost anything else on the site. Full protection is rarer and usually shorter, reserved for a live edit war between two accounts that already qualify to edit, not for shutting one side out. Extended-confirmed protection sits above both, and it isn't a response to ordinary vandalism at all. The community reserves it for pages inside a designated contentious topic: long-running national disputes, certain live political fights, subject areas where sustained disruption has already earned collective sanctions.
A company or a person's biography rarely starts out inside one of those areas. It arrives there sideways — a firm drawn into a politically charged dispute, an executive named in a controversy Wikipedia already treats as contentious elsewhere in the encyclopedia. Once that tag applies to the page, thirty days and five hundred edits stop being a formality and become a wall. A communications account opened specifically to fix one outdated fact cannot climb it in a hurry, and trying tends to make the page's history look worse, not better.
Thirty days and five hundred edits works less like a queue to wait out and more like a filter, built to catch accounts that exist for exactly one page.
Editors who notice a new account racking up five hundred scattered edits across unrelated pages in a hurry usually read the pattern correctly, and the scrutiny that follows — a look at contribution history, a question about purpose, occasionally a report to the sockpuppet investigations noticeboard — can end the account before it reaches the number it was chasing. Gaming the count is slower than earning it honestly, and considerably likelier to backfire.
Underneath all three active levels, the route that actually works doesn't require an account to age at all: a dated, sourced request on the article's talk page, addressed to whichever editor already holds the standing the page demands. Protection carries a review date at the noticeboard that grants it, too. Most of it lifts on its own once the disruption that justified it has stopped — without anyone needing to out-edit the count that put it there in the first place.
