The thirst for Baby Sussex’s name was real. So much so that some Prince Harry and Meghan Markle fans have taken to perusing the royal family website for clues. Lo and behold, they found some…or did they?
Royalists had a field day when reports surfaced that the royal family’s site featured web domains for rumored baby names like Prince Arthur, Prince Alexander and Prince James. Naturally, they assumed these names were on the Duke and Duchess of Sussex’s baby name list, which would mean the palace accidentally leaked their would-be names. Not surprisingly, Buckingham Palace nipped this speculation in the bud immediately.
“A large number of search term redirects were set up some time ago on royal.uk,” Buckingham Palace told E! News in a statement. “This was in order to improve user experience.” This makes sense. If you’re perusing the royal family website, the last thing they’d want is for you to get an error message. A redirect makes for better UE (that’s tech-talk for user experience *hair flip*).
A similar fiasco took place ahead of Prince Louis’s birth last April when the Daily Mail noted that a webpage for “Prince Albert” existed on the royal family’s website. (Obviously, this was before we knew he was named Prince Louis.)
Pages for Kate Middleton, Meghan Markle, Prince Harry, Prince William, etc. exist but if you try and access Princess Charlotte or Prince George’s page, an “access denied” message pops up. The same message was generated when Prince Albert was searched, but random names like Prince Steve (not a royal name) render a “page not found” message.
So what did we learn? Royal redirects mean absolutely nothing. Hey, at least we have our bases covered when the next mini-royal arrives.
BRB, Googling more about the historical significance of "Archie."