> For the complete documentation index, see [llms.txt](https://docs.talordata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talordata.com/serp-api/integration/plugin-integration/how-to-integrate-talordata-with-dify.md).
# How to integrate Talordata with Dify
An intelligent search data plugin powered by the Talordata SERP API, enabling Dify workflows to rapidly retrieve structured search results from engines such as Google, Bing, Yandex, and DuckDuckGo. It supports various SERP data types—including standard search results, news, images, shopping listings, and local results—making it suitable for use cases such as SEO analysis, AI agent retrieval, market research, and content research.
### **Available tools**
#### Search Engine Results
Obtain structured search results from mainstream search engines:
* Google Search
* Bing Search
* Yandex Search
* DuckDuckGo Search
#### SERP Data Modules
Retrieve different types of search result data:
* News Results: Google News、Bing News
* Image result: Google Images、Bing Images
* Video results: Google Videos、Bing Videos
* Shopping results: Google Shopping、Bing Shopping
* Local results: Google Local、Google Maps
* Recruitment results: Google Jobs
* Hotel and flight results: Google Hotels、Google Flights
* Trends and Scholar Results: Google Trends、Google Scholar
#### Search Result as Structured Data
Convert search results into clean, structured data ready for direct processing by LLMs—suitable for:
* AI Q\&A Retrieval
* RAG Data Augmentation
* Competitor Analysis
* Content Summarization
* Search Result Comparison
* SEO Ranking Monitoring
### **Use Cases**
* SEO Analysis: Track keyword rankings, competitor pages, and changes in search results
* AI Agent Retrieval: Enable AI agents to access real-time search engine results
* Content Research: Gather news, articles, blog posts, and industry materials
* Market Research: Monitor brands, competitors, products, and industry trends
* Local SEO: Analyze local search results across different cities
* E-commerce Monitoring: Retrieve shopping search results, product titles, prices, and rankings
* Sentiment & Trend Monitoring: Track search results for brand terms, industry keywords, and trending events
## **How to integrate Talordata with Dify**
{% stepper %}
{% step %}
### Install plugin
[Go to Dify](https://cloud.dify.ai/plugins) and install the Taylordata SERP API plugin via the GitHub link.
Once installation is complete, you can utilize Talordata's search capabilities within Dify Workflow to integrate real-time search results into your AI applications.
{% endstep %}
{% step %}
### Get Talordata API Token
\- Log in to your [Talordata Dashboard](https://dashboard.talordata.com/)\
\- Go to the [SERP API API Token](https://dashboard.talordata.com/scraping/serp-api/api-token) page\
\- If you haven't created one yet, please generate a new API key.\
\- Copy the API Key to complete authorization within the Dify plugin.
{% endstep %}
{% step %}
### Create your first workflow
* Go to the Dify Studio → Workflow
* Create a new workflow
* Add any Talordata SERP API tool, such as:
Search Engine — Get search results from Google, Bing, Yandex, DuckDuckGo
* Enter your API Token when prompted
* Connect an LLM node to summarize, analyze, or restructure search results.
* Finally, connect to the END node and output the processed results.
{% endstep %}
{% step %}
### Example workflow
Example use case: Search for a specific keyword and have the LLM generate a brief analysis report.
#### Workflow Example
1. START → Input: Keywords
2. Talordata Search Engine → Get search results
3. LLM → Analyze search results to extract key insights, primary sources, and rankings.
4. END → Output: Structured search analysis report
{% endstep %}
{% endstepper %}
{% hint style="info" %}
### Important Notice
* Each step in the workflow should reference the output of the previous step.
* If the input keywords are long, it is recommended to set the input field type to "short paragraph."
* If you need to analyze multiple keywords, you can use a loop node or batch input.
* For localized search, please configure parameters such as country, language, city, and device.
{% endhint %}
### **Advanced Options: Use Talordata MCP Server**
In addition to invoking the Talordata SERP API in Dify via plugins or HTTP Request nodes, advanced users can also integrate using the [Talordata MCP (Model Context Protocol)](/serp-api/mcp-server.md).
Talordata MCP encapsulates the search capabilities of the SERP API into MCP tools that can be invoked by AI tools. This enables Dify workflows or external agents to seamlessly access search data capabilities—such as real-time search, result analysis, ranking comparisons, and competitor monitoring.
In Dify, you can invoke Talordata MCP using custom tools, HTTP request nodes, or external service nodes, and then pass the data returned by the MCP to an LLM node for further processing.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.talordata.com/serp-api/integration/plugin-integration/how-to-integrate-talordata-with-dify.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.