Skip to content

Add post-deploy workflow to notify search engines#391

Open
Copilot wants to merge 3 commits intomainfrom
copilot/add-post-step-update-search-engines
Open

Add post-deploy workflow to notify search engines#391
Copilot wants to merge 3 commits intomainfrom
copilot/add-post-step-update-search-engines

Conversation

Copy link
Contributor

Copilot AI commented Mar 17, 2026

After each successful GitHub Pages deployment, search engines should be notified to crawl updated content. Adds a notify-search-engines workflow triggered on pages-build-deployment success.

Changes

  • .github/workflows/notify-search-engines.yml — new workflow with:
    • workflow_run trigger scoped to pages-build-deployment completions, conditional on success
    • Google Indexing API notification via robingenz/google-indexing-action@v1.0.2 (GCP_SERVICE_ACCOUNT_JSON secret)
    • IndexNow submission (Bing, DuckDuckGo, Yandex) via bojieyang/indexnow-action@v2.1.0 against the published sitemap (INDEXNOW_KEY secret)
    • permissions: {} — no GITHUB_TOKEN access needed
    • Actions pinned to specific version tags instead of mutable refs (@main, @v2)

Required Secrets

Secret Used by
GCP_SERVICE_ACCOUNT_JSON Google Indexing API
INDEXNOW_KEY Bing / DuckDuckGo / Yandex via IndexNow
Original prompt

This section details on the original issue you should resolve

<issue_title>Add post step to update search engines</issue_title>
<issue_description>Post docs new publish google search and bing and perhaps other search engines should be notified.

E.g.

# Google Indexing
      - name: Notify Google
        uses: robingenz/google-indexing-action@main
        with:
          siteUrl: 'https://docs.falkordb.com'
          gcpServiceAccountKey: ${{ secrets.GCP_SERVICE_ACCOUNT_JSON }}

      # Bing + DuckDuckGo + Yandex via IndexNow
      - name: Notify Bing (IndexNow)
        uses: bojieyang/indexnow-action@v2
        with:
          sitemap-location: 'https://docs.falkordb.com/sitemap.xml'
          key: ${{ secrets.INDEXNOW_KEY }}

      # Generate IndexNow key file during build
      # (add this BEFORE your pages deploy step)
      # - name: Setup IndexNow key file
      #   run: echo "${{ secrets.INDEXNOW_KEY }}" > ./site/${{ secrets.INDEXNOW_KEY }}.txt
```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: gkorland <753206+gkorland@users.noreply.github.com>
steps:
# Google Indexing
- name: Notify Google
uses: robingenz/google-indexing-action@v1.0.2

Check warning

Code scanning / CodeQL

Unpinned tag for a non-immutable Action in workflow Medium

Unpinned 3rd party Action 'Notify Search Engines' step
Uses Step
uses 'robingenz/google-indexing-action' with ref 'v1.0.2', not a pinned commit hash

# Bing + DuckDuckGo + Yandex via IndexNow
- name: Notify Bing (IndexNow)
uses: bojieyang/indexnow-action@v2.1.0

Check warning

Code scanning / CodeQL

Unpinned tag for a non-immutable Action in workflow Medium

Unpinned 3rd party Action 'Notify Search Engines' step
Uses Step
uses 'bojieyang/indexnow-action' with ref 'v2.1.0', not a pinned commit hash
Copilot AI changed the title [WIP] Add post step to update search engines Add post-deploy workflow to notify search engines Mar 17, 2026
Copilot AI requested a review from gkorland March 17, 2026 06:31
@gkorland gkorland marked this pull request as ready for review March 22, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add post step to update search engines

2 participants