Blue Raven installs like any other WordPress plugin, and it does nothing until you switch a tool on. That second part is deliberate. Installing a plugin is not the same as agreeing to every feature in it changing what a search engine sees.
What it needs
WordPress 7.0 or later and PHP 8.0 or later. Both are checked against the plugin header before WordPress will activate it, so an older host refuses the activation with a message rather than installing something that will break on the next page view.
There is no account, no licence key and no connection to us. The plugin page carries the same requirements if you want them without installing anything.
Install it
From the dashboard, go to Plugins, then Add New, and search for Blue Raven. Install and activate.
If you have the zip, Plugins, Add New, Upload Plugin does the same job. Either way you land on the same place, and nothing on the front end of the site has changed yet.
WP-CLI works too.
wp plugin install blue-raven --activate
First run, and where to start
The plugin adds one menu item with four screens. The overview screen is the one to read first, because it checks the site rather than listing features. It will tell you, for example, that the sitemap is off, or that a page is missing a description. Each finding links to the tab that fixes it.
Then switch on what you actually came for. The common order is meta tags, then the sitemap, then forms, because a sitemap is only worth submitting once the titles and descriptions on the pages are worth reading.
Adding a form to a page
Build the form on the Forms screen, save it, and copy the shortcode it gives you into the page or post where the form belongs. The form id is in the shortcode, so a page can carry two different forms without them colliding.
Send a test submission to yourself immediately. A form that looks right and delivers nothing is the failure this step exists to catch, and it is quick to find when the form is one page old rather than six weeks old.
What deleting the plugin does
By default, nothing is removed. The switch that drops the tables and the settings row is off, so deleting the plugin leaves your entries and your configuration in the database. That is the safe default, because a site that deletes a plugin to test something should not lose a year of submissions to find out.
If you do want the data gone, turn the switch on before you delete, and read the list beside it. It names the tables it will drop.
When something does not work
The readiness screen is the first place to look, because most of what goes wrong is a setting that was never switched on rather than a fault. If a form is not delivering, the send path is the second place to look, and the mail settings are covered in how to send form mail through SMTP.
If a real person is being refused at the form, the anti-spam checks are the cause and they are covered in a form submission was blocked. Those two articles answer most of the first week.
EnterraHost