RanklyBee

List the signed-in user's Projects with their role and websites. Start here to get a projectId.

無需輸入參數。

List the signed-in user's Projects and their active Site details so the user can choose a target without knowing an internal Project ID.

無需輸入參數。

Read the current active Site's backlink submission profile and readiness state.

List visible, available backlink sources that have a supported submission destination.

Check paid access, profile confirmation, source policy, inventory, duplicate backlinks, and daily capacity before creating a submission job.

After user review and approval, create one idempotent submission job in waiting_human state. This does not click the third-party site's final submit button.

Read the current state and recorded outcome of a backlink submission job.

Record the result after a user-approved browser interaction. Use needs_verification for CAPTCHA, MFA, email verification, rate limits, or ambiguous results.

List scored leads for a Project, newest first. Filter by tier (hot, warm, explore), stage, platform, or text. Each lead has the evidence quote that shows the buying intent and a link to the original post.

Read one lead with its score, evidence quote, reason, stage, and link.

List the monitoring keywords (search phrases and platforms) for a Project.

Move a lead to to_qualify, to_contact, in_conversation, or closed. This fires any stage-changed automations the user configured.

List the websites in a Project. Most tools need a siteId from this list.

Read what Ranklybee knows about a website: positioning, audience, products, competitors, and the latest analysis job.

Replace the editable site profile. Read it with get_site_profile first and send every field back, changing only what the user asked for.

Crawl the website again and rebuild its profile. Runs in the background; poll get_site_profile for the result.

Read how much of each plan allowance the Project has used in the current period.

Read the latest content plan for a website with its scheduled article briefs. Returns null when no plan exists.

Generate a new content plan from the site profile and keyword research. Uses the plan's content allowance.

Start a reviewed content plan so its briefs are written on their scheduled dates.

Approve or reject a whole content plan.

Approve or reject one article brief in a content plan.

Move an article brief to another date (YYYY-MM-DD) on the content calendar.

Set the notes the writer follows for one article brief. Send an empty string to clear them.

Change the target keyword of one article brief.

Look up keyword ideas for a seed phrase with volume, difficulty, and whether each is already in the plan. The ideas are saved to the website's keyword list.

List the keywords saved for a website's articles.

Add keywords to the content plan as article briefs, optionally on a given date. Returns the keywords that were skipped and why.

Save keywords to the website's keyword list without scheduling articles for them.

Remove keywords from the website's saved keyword list.

List a website's articles, newest first, with their state and publication. Each item is large, so pass a small limit such as 10 and page with offset.

Read one article with its full content, quality checks, and publication state.

Write the article for an approved brief. Uses the plan's article allowance and takes a few minutes; poll get_article.

Replace an article's editable content. Read it with get_article first and send every content field back.

Rewrite the chosen fields of an article with AI.

Send a draft article to the approval step.

Approve or reject an article that is waiting for approval.

List the CMS connections an article can be published to.

Publish an approved article to a connected CMS. The article goes live on the user's website, so confirm with the user first.

Record the live URL of an article the user published by hand, after checking the page.

Delete an article from Ranklybee. This does not remove a page already published on the website.

Read the refresh opportunities found for published articles and the state of each improvement.

Scan published articles against search data for new refresh opportunities.

Write the improved version of an article for one opportunity.

Replace the drafted content of an improvement. Send every content field back.

Send a drafted improvement to the approval step.

Approve or reject an improvement that is waiting for approval.

Apply an approved improvement to its article. Confirm with the user first.

Compare search performance before and after an applied improvement and record the result.

Dismiss an improvement opportunity with a reason.

Read the automatic writing and publishing schedule for a website.

Replace the automatic writing and publishing schedule. Read it with get_content_automation first; auto_publish_approved publishes without a human review.

Read the writing preferences for a website: voice, structure, images, linking, and improvement rules.

List the pages articles are allowed to link to.

Add a page of the website that articles should link to.

Stop articles from linking to a page.

List the products articles can feature.

Add a product to the catalog. Pass imageStorageKey as null.

Replace a product's fields. Send every field back.

Set whether articles may feature a product.

Delete a product from the catalog.

Read totals for tracked backlinks, their health, and open replacement tasks.

List the backlinks Ranklybee tracks for a website, with status and latest check.

Start tracking a backlink: the page that links (sourceUrl) and the page it links to (targetUrl).

Fetch the linking page and record whether the backlink is still live.

Queue a live check for every tracked backlink of a website.

Change the status or notes of a task opened for a lost backlink.

Close a tracked backlink with a reason.

Read whether the website's existing backlinks have been imported.

Import the website's existing backlinks so duplicates are detected.

Search Ranklybee's library of directories and other backlink sources, with quality, pricing, and link type.

Read prospect counts by status for a website.

List link prospects with scores, status, and contact. Filter by status, keyword, or Domain Rating.

Read the Domain Rating range and page types used to find prospects.

Replace the settings used to find prospects. Send every field.

List the keywords used to search for link prospects.

Add keywords to search for link prospects.

Remove one prospecting keyword.

List the pages the user pitches in outreach.

Add or update a page worth pitching, with what makes it link-worthy.

Add a page as a link prospect and score it.

Search the web for link prospects. Runs in the background; poll get_prospect_discovery with the returned job. Uses the plan's prospecting allowance.

Find prospects among the sites that link to the given competitor domains. Runs in the background.

Read the progress and result counts of a discovery job.

Reject one prospect, or block its whole domain from future discovery (a reason is required to block).

Allow a previously blocked domain to appear in discovery again.

List the people found for outreach, with email verification status.

Add a contact by hand.

Check whether a contact's email address is deliverable.

Look up who to email at a prospect's site. Uses the plan's contact allowance.

Set which email address outreach to a prospect goes to.

Add a contact to the do-not-email list with a reason.

List the email templates available for outreach.

Create an email template.

Replace an email template's content.

Delete an email template.

List the sender identities and templates a new draft can use.

List outreach threads in one bucket (ready, queued, sent, or replied) with their draft and latest message.

Write a first email to a prospect's contact from a template and sender. Nothing is sent.

Write a first email to a prospect's contact, letting Ranklybee pick the sender and template. Nothing is sent.

Replace the subject and body of an unsent draft.

Rewrite an unsent draft following an instruction.

Record that the outreach earned a link and start tracking that backlink.

Close an outreach thread that did not earn a link.

Reopen a thread that was marked won or lost.

Read scheduled and sent emails, sender limits, and replies waiting for review.

Set the sending window, weekdays, and daily limit for one sender identity.

Schedule a drafted thread with up to two follow-ups. mode=live emails a real person from the user's mailbox; show the user the exact email and get approval first. mode=simulation sends nothing.

Schedule several drafted threads at once. mode=live emails real people; get the user's approval of every email first.

Send a message in an existing outreach thread from the user's mailbox. Get the user's approval of the exact text first.

Act on a reply Ranklybee drafted for an inbound email. action=send emails a real person; get the user's approval first.

Cancel the remaining emails of a scheduled sequence.

Read what the outreach agent did over the last 7, 30, or 90 days.

Read whether the outreach agent is running and its limits.

List recent runs of the outreach agent.

List the cases the outreach agent stopped on and left for a human.

Pause or resume the outreach agent. While active it finds prospects and sends emails on its own.

Change the status or notes of an exception.

Read lead counts by tier and stage, the monitor state, keywords, and customer profiles.

Read how often and where the brand is mentioned.

List collected posts that matched a keyword, including brand mentions that are not leads.

Search the monitored platforms now and score what is found. Uses the plan's lead scan allowance.

Tell Ranklybee whether a lead was a good match so scoring improves.

Add or remove a lead from the user's favorites.

Hide a lead that is not relevant.

Bring back a dismissed lead.

Draft a reply to a lead's post in the chosen tone. Nothing is posted; the user posts it themselves.

Edit a drafted reply, or record that the user posted or dismissed it.

Add a keyword to monitor, with its search phrases and platforms.

Replace a monitoring keyword's phrases and platforms.

Pause or resume monitoring for one keyword.

Delete a monitoring keyword.

Add a customer profile that leads are scored against.

Replace a customer profile.

Delete a customer profile.

Set which platforms are searched for leads.

Set how often leads are scanned and whether the monitor is active.

List the rules that notify the user about new leads.

Create a rule that notifies a channel when matching leads arrive.

Pause or resume one alert rule.

Delete an alert rule.

Read how often AI assistants mention the brand: visibility, share of voice, position, and trend.

List the tracked prompts with visibility, position, and the brands each answer names.

List the recorded answers for one prompt across AI engines.

Read the ranking of brands in AI answers, share of voice, and head-to-head prompts.

Read one brand's visibility against the user's, with the prompts and sources behind it. brandKey comes from get_ai_visibility_competitors.

Read which domains and pages AI answers cite, and the domains that never mention the brand.

List the pages of one domain that AI answers cite.

Read how positively AI answers describe the brand and the themes driving it.

Read one sentiment theme with quotes and suggested tasks; the summary and tasks are written on first read. themeKey comes from get_ai_sentiment_overview.

Compare how favorably AI answers describe the brand and its rivals.

Read the full text of one recorded AI answer.

Ask AI for prompts worth tracking for the website. Nothing is tracked until you create them.

Add a prompt to track across AI engines. Counts against the plan's prompt limit.

Add up to 100 prompts at once. Counts against the plan's prompt limit.

Replace a tracked prompt's settings.

Pause or resume tracking for one prompt.

Ask the AI engines one tracked prompt now and record the answers.

Delete a tracked prompt and its history.

Leave a brand out of competitor comparisons.

Bring an excluded brand back into competitor comparisons.

Save a brand seen in AI answers as a competitor in the site profile.

Create a topic to group prompts.

Rename a prompt topic.

Delete a topic. Its prompts are kept.

Move prompts into a topic, or pass topicId null to ungroup them.

Mark a suggested sentiment task as done or not done.

Read Google Search Console clicks, impressions, top queries and pages, and whether the property is connected.

Pull the latest data from Google Search Console.

Read the latest search health report and open alerts for a website.

List pages that rank but get fewer clicks than expected.

Fetch a page and review its title and meta description against the queries it ranks for.

List the on-page changes logged for a website and their measured effect.

Record a change made to a page so its effect on search performance is measured.

List the traffic drop diagnoses run for a website.

Read one traffic drop diagnosis with its findings.

Analyze a year of search data for the cause of a traffic drop, optionally for a date range (YYYY-MM-DD).

Read whether social distribution is connected and which accounts post.

List the website pages that can be turned into social posts.

Read the talking points extracted from a page for social posts.

Read a page and extract talking points for social posts.

List the social distribution campaigns of a website.

Read one campaign with its schedule and posts.

Create a draft campaign that turns a page into scheduled social posts.

Replace a draft campaign's settings.

Start a campaign so its approved posts are published on schedule. Confirm with the user first.

Pause a running campaign.

Resume a paused campaign.

Cancel a campaign and remove its unpublished posts from the connected social scheduler.

List social posts by campaign, status, or platform.

Approve posts for publishing to the user's social accounts. Show the user each post first.

Replace a post's text and approve it for publishing.

Reject posts so they are not published.

Write a post again with AI.