Verify search visibility after each GitHub deployment
Turn a successful production deployment into an immediate Semrush indexed-pages check, with the findings delivered in the channel you already use.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Get indexed pages
Retrieves a list of indexed pages from semrush for a specified `target` (root domain, domain, or url) and `target type`, ensuring `target` is publicly accessible, semrush-analyzable, and correctly matches `target type`.
Why this helps
Shipping consumes all available attention, so the follow-up check for whether important pages remain visible in search is easy to postpone indefinitely.
- Pairs release completion with a concrete SEO verification
- Surfaces unexpected indexed-page changes without opening another dashboard
- Creates a repeatable handoff from engineering to growth
Setup
Build it in a few focused steps.
- 1Connect GitHub and Semrush to Notis once in the portal.
- 2Create an automation and prompt Notis to check Semrush indexed pages for the production domain after a successful deployment status.
- 3Pick New Deployment Status Created as the trigger and tell Notis to continue only for production successes.
- 4Choose the channel for concise run reports and test it with one real production deployment.
Questions about this workflow
Can the report focus on a specific domain or subdomain?
Yes. Name the public target and target type in the plain-language prompt so Notis requests the appropriate Semrush report.
Will failed deployments run the SEO check?
Not if the prompt tells Notis to act only when the deployment status is successful.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Semrush. A trigger fires from one place; an action lands in another.
GitHub triggers
Semrush actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Get ad copies
Retrieves unique ad copies semrush has observed for a specified domain from a regional database, detailing ads seen in google's paid search results.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Get anchor texts
Use this action to get a csv report of anchor texts for backlinks pointing to a specified, publicly accessible domain, root domain, or url.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get authority score profile
Retrieves the authority score (as) profile for a specified target, showing the count of referring domains that link to the target for each as value from 0 to 100.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get backlinks
Fetches backlinks for a specified domain or url as a csv-formatted string, allowing customization of columns, sorting, and filtering; ensure `display limit` surpasses `display offset` when an offset is used, and note the `urlanchor` filter may have limitations for targets with extensive backlinks.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Backlinks overview
Provides a csv-formatted summary of backlinks, including authority score and link type breakdowns, for a specified and publicly accessible domain, root domain, or url.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Batch comparison
Compares backlink profiles for multiple specified targets (domains, subdomains, or urls) to analyze and compare link-building efforts.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Batch keyword overview
Fetches a keyword overview report from a semrush regional database for up to 100 keywords, providing metrics like search volume, cpc, and keyword difficulty.
Commit Event
Triggered when a new commit is pushed to a repository.
Broad match keyword
Fetches broad match keywords for a given phrase; `display sort` and `display filter` parameters are defined but currently not utilized by the api call.
Connect any two apps with Notis in the middle.
Not just GitHub and Semrush. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Semrush.