Use Orova SEO
one step at a time.

Open the Projects section. Click Projects in the tab bar at the top. The table shows the columns Project ID, Created by, Created and Last updated. Clicking a project name opens its detail page.

Click Create project. The Create project button sits in the top right corner. One click creates the project straight away — no window asks for a name — and Orova takes you to its detail page, with a banner reminding you that the next step is connecting your website and Google.

Rename the project. On the detail page, click the project name to edit it. The name must be 2 to 200 characters. Naming it after the website makes it easier to recognize. A name that is too short or too long is rejected and nothing is saved.

Click Connect WordPress. On the project detail page, in the publishing target block, click Connect WordPress. A window opens and asks for the WordPress login page URL. If the project is already connected, the WordPress card shows Connected with a trash icon instead of the connect button — click the trash icon to disconnect first if you want to connect again.

Paste the login page URL. This is usually your website address plus the familiar login path. If your website hides the default admin path, paste the exact custom path you use.

Follow the two steps in the same window. The two steps appear right inside the Connect WordPress window — there is no separate page: step one is Log in to WordPress (it opens in a new tab), step two is Open the authorization page. Do them in that order.

Approve on the WordPress side. WordPress shows a page asking you to grant access to an application named Orova. Click the WordPress approval button. The browser returns to Orova on its own and the project shows as connected.

Check it. Go back to the project detail page. The WordPress card should now show Connected with a trash icon next to it. If you still see the Connect WordPress button, the approval step didn't complete — start over.

Click Connect via API. In the same publishing target block, click Connect via API. The form shows two fields.

Fill in the API endpoint. The Your website API endpoint field takes the address your website exposes to receive articles. Your technical team provides this address. This endpoint must answer the list and get actions so Orova can read your existing articles (to avoid duplicates, add internal links and optimize posts) — see the technical guide at /docs/publish-api.

Fill in the secret token if you have one. The Secret token field is the secret string your website uses to recognize Orova. Leave it blank and Orova generates a key for you to copy over to your website.

Save the connection. Click the connect button. Orova saves it and the publishing target block switches to the connected-via-API state.

Click the connect button on the row you want. Search Console, for example. An explanation window opens, lists the steps ahead and states clearly that Orova only requests read access.

Choose a Google account. Click continue and the browser moves to Google's screen. Choose the account that has permission to view that website's data. Pick the wrong account and no website will show up to select afterwards.

Allow. Google lists the permissions Orova is asking for. Click allow. The browser returns to Orova on its own.

Pick the right website or property. If your Google account manages several websites, Orova shows a list to choose from. Pick the project's website and confirm. That row switches to Connected.

Open Manage files. Once Drive is connected, click Manage files on the Drive row. The page listing the files already read opens.

Add files. Pick the Drive files you want Orova to reference: your company profile, product sheets, brand naming rules.

Re-read when a document changes. After you edit a file on Drive, ask Orova to read it again so it stays current. That re-read calls AI, so it uses quota; the number of credits appears before you confirm.

Click Create your own voice. The button sits right inside the AI Voice section on the project detail page. A window opens with three fields, all required.

Fill in Voice name. Name it so you recognize it when picking elsewhere — after the brand, for instance, or after the type of article.

Fill in Short role. One sentence describing who the writer is. For example: a consultant explaining things to a customer who is looking into this for the first time.

Write the Style instructions. This is the most important part — it's literally the brief for the AI. The more specific, the closer the match: the article structure you want, sentence length, words to use, words to avoid, whether personal opinions are allowed.

Save and select it. Once saved, the new voice appears in the list tagged Yours. Select it to make it the project default. Each keyword can still use a different voice when you add it.

Part 1 — Keyword and project. This part is required. Fill in Keyword (2–255 characters), choose the Project (website) it will publish to, choose What searchers want on Google, then pick the AI writing voice and Article language. The voice list has two groups: built-in voices and your voices.

Part 2 — Guidance for Orova to write. Skippable. The A specific angle you want to focus on field lets you aim the article at a narrow angle. The outline and extra-notes field lets you hand over the structure you have in mind.

Part 3 — Length and number of images. The defaults are fine. Here you set the word count you want and how many images go into the article.

Part 4 — Reference documents. The list of Drive files Orova has read for that specific project. Tick a file and this article references it. An empty list means the project hasn't connected Drive or hasn't added files yet.

Part 5 — When to publish. Choose Publish as soon as possible to go straight into the queue, or Schedule publishing to set a timetable. See the scheduling part just below.

Save. Click save. The keyword appears in the table with the Queued status. No article is written at this step.

Open Import from Excel. Click Import from Excel. The window opens with a button to download the template.

Download the template and fill it in. Download the template file and put one keyword per row in the columns provided. Don't rename the columns.

Choose the shared settings. In the window, choose the project, the shared voice and the shared reference documents for the whole batch.

Upload the file. Pick the file and upload it. The file can be up to 8 MB. When it's done, Orova reports how many rows were imported, how many were invalid, and how many were skipped because quota ran out.

Pick a period. At the top of the screen you get 28 days, 7 days, 90 days, 6 months, 1 year, and Custom date range to set From – To yourself, then click Apply.

Click Refresh metrics. This button calls Google for the latest numbers. When it finishes, the table reloads itself. It uses no AI quota, because it only reads Google data.

Set up automatic refresh. Click Auto to open a small panel: choose how many days of data to fetch and how often to refresh. The panel states clearly that no AI quota is used.

Download Excel if you need it. The Download Excel button exports exactly the table you're looking at, so you can send it on or archive it monthly.

Send weak articles to Optimize. In the Actions column, click Add to Optimize for an article that ranks near the top but gets few clicks. It waits in the Optimize section and nothing runs until you start it.

Open the Optimize tab. In the tab bar at the top of the module, click Optimize. The top of the page shows three counters: Total, Waiting, Done. Below them is the table of posts in the queue.

Put posts into the queue. There are three ways. One, click Add posts and paste post links — several rows at once is fine. Two, click Upload file and send an Excel or CSV file built from the sample sheet you can download there. Three, from the Reports tab or the Analysis tab, click Add to Optimize right on the post's row.

Pick a goal for each post. Every row has an Optimization goal box. Click it to open the list of six goals. If you are not sure which one to pick, leave it on Auto — AI decides.

Run one post or run them all. Click the run button on a row to handle that post alone. Click Run all to work through every waiting post. Each post takes a few minutes and runs in the background, so it finishes even if you close the tab. The row status switches to optimized when it is done.

Turn on auto-optimize if you would rather not click. Flip the Auto-optimize switch at the top of the page. Orova then scans the queue every 5 minutes and runs the waiting posts for you. Turning the switch off stops it; a post already mid-run finishes anyway.

Filter when the queue gets long. Use the status filter and the Optimization goal filter above the table to find posts quickly. Removing a post from the queue does not touch the post on your website.

Click Analyze now. Pick Analysis in the tab bar at the top, choose a project and click Analyze now. From then on the button is called Update. The run takes 2–4 minutes in the background, so the results are waiting for you even if you close the tab.

Read the row of counters at the top. Six counters show the total number of posts, how many Orova wrote, how many get impressions on Google, how many need optimizing, how many topic clusters there are and how many posts are grouped. That row alone gives you the big picture.

Open Article list and look at the Priority column. Open the Article list tab. The priority column is the one worth your attention. Start with the P1 - Golden opportunity posts — those are the closest to the top.

Send new keywords to the writing queue. Open the New keywords tab. Tick the rows worth writing and click Add keywords. They go straight into the queue of the Write tab; nothing is written yet.

Push weak posts to Optimize, or merge them. Tick several posts and click Add to Optimize to move them into the optimize queue. Or click Merge into 1 post — the post you tick first becomes the main one.

Let Orova re-analyze on a schedule. Click Auto to set a recurring run. The dialog states plainly that this uses AI quota, same as Update.

Add a competitor to the list. Pick Competitors in the tab bar at the top, stay on the List tab and click Add competitor. Fill in the Website address * box — that one is required. The name and the note are optional; add them so the row is easier to recognize. Save, and the competitor appears as a row in the table straight away.

Click Scan competitors so Orova goes and reads. Click Scan competitors. Orova visits every website in the list and collects their most recent posts. It runs 1–3 minutes in the background, so closing the tab is fine. When it finishes, open the Posts tab to see the posts with their publication dates.

Click Orova evaluation to get suggestions. Come back and click Orova evaluation. The AI reads the posts just scanned and derives the topics you should write. It runs 1–2 minutes in the background and uses quota.

Go through the Suggestions table, then push them to the writing queue. Open the Suggestions tab. Read the reason and priority columns, tick the rows worth doing and click Add. The keywords go straight into the queue of the Write tab; nothing is written yet.

Cap how many suggestions you get each time. The Max suggestions box decides how many keywords an evaluation returns at most. Keep the number small when you only want a few solid ideas.

Click Run health check. Pick Site Health in the tab bar at the top, choose a project and click the run button. It takes 1–2 minutes in the background and finishes even if you close the tab. From then on the button is called Run again.

Read the overall score first, the group scores second. On the Overview tab, look at the overall score out of 100 for the general picture. Then read the detailed score by group to see which group is dragging the number down.

Look at the Loading speed section. Open the Loading speed tab. Google scores Mobile and Desktop separately, with four figures on each side: Speed, SEO compliance, Accessibility, Best practices. Fix the mobile side first, because most readers are on phones.

Read the three experience figures. The same tab has three more lines: Main content shows, Stable layout, First text shows. They measure how the page feels to a visitor — how long before any text appears, and whether the layout jumps around.

Run the check again once things are fixed. Every warning spells out what needs fixing. Send the list to whoever maintains the website, and once it is done click Run again so the score reflects the new state.