Proxy Integration Guide · SEO Tool
Enhance your Semrush data collection with reliable residential proxies. Track rankings, analyze competitors, and gather keyword data without restrictions.
A card is required. A paid 10 GB plan starts after 7 days unless you cancel. View trial terms.
# Python example
proxies = {
"http": "http://user-country-us:[email protected]:12286",
"https": "http://user-country-us:[email protected]:12286"
}Recommended: Rotating Residential Proxies
Semrush data scraping benefits from residential IPs that rotate automatically. This prevents detection while allowing large-scale keyword research and competitor analysis.
For maintaining persistent Semrush sessions
For high-volume API requests
Sign up and choose a residential proxy plan that fits your data collection needs.
Add proxy configuration to your scraping setup with geo-targeting if needed.
1# Python example2proxies = {3 "http": "http://user-country-us:[email protected]:12286",4 "https": "http://user-country-us:[email protected]:12286"5}Add natural delays between requests to maintain high success rates.
Track success rates and adjust rotation and targeting settings as needed.
Gather comprehensive keyword data including search volumes and difficulty scores.
Monitor SERP positions for your keywords across different locations.
Collect backlink profiles for competitive analysis and link building.
Analyze competitor traffic sources and top-performing pages.
Target specific countries, states, or cities for localized SERP data.
HTTPS support ensures your data collection is encrypted and secure.
Sticky sessions up to 120 minutes for multi-step data workflows.
Residential IPs minimize blocks, maximizing your data yield.
Use rotating residential proxies, implement natural request delays (3-5 seconds), and vary your request patterns. Residential IPs get blocked less often than datacenter IPs.
Yes. Residential proxies target down to city level, so you can collect SERP data as searchers in a specific city see it.
For Semrush scraping, rotating IPs every 1-3 requests works well. For continuous sessions (like exporting reports), use sticky sessions.
Yes, our proxies work with Semrush API calls. Datacenter proxies can be more cost-effective for pure API usage.
Any tool that accepts an HTTP or SOCKS5 proxy works. These have their own setup guides.
Get started with our reliable proxy network. Scale your SEO research with rotating residential IPs worldwide.
A card is required. A paid 10 GB plan starts after 7 days unless you cancel. View trial terms.
Find connection settings, plan comparisons and checks you can run with your own pages before a larger order. Open the guide to choose a topic or follow the setup steps.
These examples show which settings and checks to keep when you want to use the same setup again.
| What to save | Before | After |
|---|---|---|
| Settings | An endpoint is pasted without notes. | Save the country, protocol and session settings with the application. |
| Page check | Only the connection status is checked. | Open the page and check its location and required fields. |
| Errors | The full page list is rerun after an error. | Save failed URLs and retry the ones that need another attempt. |
Choose the country or city you want to check in the residential endpoint generator, then use that endpoint in the browser or supported search tool. Keep the search language, device type and account state consistent. For a city comparison, change the location while keeping the keyword and other settings the same. For a weekly ranking check, use the same list of queries and record when each search was made.
Separate organic listings, paid placements and map results in the report. A map result and an organic link have different positions on the page, and mixing them makes changes hard to interpret. Save the query spelling, requested location and visible result URL beside the recorded position. If a ranking moves, open a small sample manually and check whether the tool counted a different page feature. Search results can also change during the day, so compare similar times when that matters to your report. Use the search provider's supported access methods and limits for collection. A proxy supplies the requested connection location; the rest of the search settings still need to be chosen in the browser or tool.
Standard residential proxies support country, state and city targeting through the endpoint generator. Start by selecting the country. Add a state or city when you are checking something local, such as a delivery area or a city-specific search page. A national catalogue check can often use country targeting. Keep the selected location with the generated endpoint so a colleague can tell which market that connection is intended to check.
After connecting, check the exit IP's reported location and open the target website. Look at the website's own location settings too. A saved delivery postcode, account address or language preference may take priority over the IP. For a local delivery test, set the postcode deliberately and keep it the same on repeat visits. If the result looks wrong, try a clean browser profile and compare the requested location with the site's displayed country. IP lookup databases can disagree, so include the lookup service and the actual page result when contacting support. Static ISP and datacenter location choices depend on current stock; their order form shows which country and city allocations are available.
Choose a short list of pages that reflects your project. For a shopping-site check, include a category page, a product with several variants and a product that is unavailable. For a localized website, include the homepage and a page where language or delivery options change. If you need several countries, run the same checks in each one. These examples show whether the setup handles the parts of the site your project actually uses.
Write down the fields you expect before running the test. Open a few results manually and compare them with the values saved by the script. Look for missing prices, unexpected currencies, duplicate products and pages that show a login prompt. Repeat a small part of the test after changing just one setting, such as the requested city or session type, so you can see its effect. Save the working endpoint configuration with the password removed. Also try a deliberately unavailable page to check that your application records the error and moves on. Once the sample works, use its traffic consumption and completion time to estimate the size and schedule of the full run.
Choose rotating residential connections for checks that can finish independently, such as reading separate public product pages. Generate a rotating endpoint in the dashboard and use it in the application making those requests. Each result should include the page address and the time it was fetched, so you can find the original page if something looks wrong. Check how your client reuses network connections when you need a fresh exit for a new request.
A login, shopping basket or multi-page form usually needs more continuity. Choose a sticky session for those steps and keep the same browser profile until the task is finished. Switching the IP during a login can cause another verification prompt or interrupt the session. When a request fails, read the error before changing the IP. Incorrect credentials need correcting, and a broken page selector needs updating. For a temporary timeout, retry a limited number of times with a delay. Keep the destination's rate limits in place across all connections. Rotating addresses should be part of a planned request schedule, with unfinished URLs saved so you can retry them without downloading the whole list again.
Check whether the service already offers an API for the information you need. Product identifiers, stock fields or other structured records may be easier to retrieve through a supported API than by reading a page. Look at the available fields, account access, update schedule and request limits. A browser remains useful when you need to see the actual page, such as its layout, language, images or the offer shown after selecting a delivery area.
For a shop review, you might use an API to maintain a product list and then open selected products in a browser to inspect their presentation. Keep the two parts connected with the product identifier. Check the permitted uses and retention terms of the source before collecting data. If you use a proxy with a browser or API client, test that client's connection settings and authentication separately from the destination's own login or API key. Include maintenance in the choice: a page redesign can change selectors, while an API version change can alter fields. Keep a short test that checks the fields your application depends on so you can spot either kind of change before a full run.
The amount of traffic depends on what your application downloads. A browser may load the page, images, fonts, scripts and background requests. A script that only retrieves the HTML can use much less. To estimate your standard residential plan, run a small batch with the same client and settings you intend to use later, then check the change in traffic usage in your dashboard.
As a calculation example, if 100 completed page checks use 20 MB, 10,000 similar checks would use about 2,000 MB, or 2 GB. This is an example of the arithmetic; measure your own pages because a photo-heavy page and a short text page can differ considerably. Include repeat visits and retries in the estimate. If you only need text, check whether your browser tool can skip unnecessary images or video, then confirm that the required text still loads. Keep images enabled for visual checks such as banner or layout reviews. Review traffic again after a website redesign or a change in your script, since either can alter how much gets downloaded on every visit.
Check the error returned by your client before starting another request. A proxy authentication error usually points to the credentials or the way they were entered. A timeout can involve the proxy connection, the destination or your own network. If a website loads but the expected price or heading is missing, inspect the page content and the selector used by your script. Keeping these errors separate makes the next step much clearer.
For a temporary connection failure, use a small retry limit and a delay between attempts. Save the failed URL so it can be retried later without running the whole list again. If the destination returns a rate limit, follow its retry instructions and reduce the request rate. Stop and review access when the site rejects the requested operation. Be especially careful with forms, orders and account changes: a timeout after submission can occur even though the change succeeded. Check the account before submitting the same action again. When contacting support, include the time, client, protocol and response message, with the password removed. A single request that reproduces the problem is more useful than a log full of repeated failures.
Before saving a setup, a team may paste a proxy into a browser, open a page and leave the settings in that one window. The next person then has to find the endpoint, choose a location and repeat the checks. A saved setup is easier to use again: give the profile a clear name, keep the credentials in protected settings and record the country, session type and test page beside it.
For example, a shop team checking its German catalogue could save a German residential endpoint, a browser profile with German language settings and a delivery postcode used for the test. Keep a product URL and the fields to check, such as price, currency and stock status. On the next visit, open that profile and repeat the same check before starting the full product list. If a result differs, you can inspect the saved settings and the page instead of guessing which connection was used. Update the notes when the shop changes its page layout or the team changes its test location. This also gives a colleague enough information to continue while the original operator is away.
For a scheduled collection job, keep a short summary of each run: pages attempted, pages completed, errors and the fields that were missing. A price-monitoring script should tell you when it saved a product without a price or currency. A localized website check should report an unexpected country or language. These checks catch problems such as a changed page layout that can leave the network connection working while the saved data becomes incomplete.
Keep the application version and selected location with the run summary. When a result changes, compare it with a recent run using the same page list and settings. If the new run includes many more pages, allow for that difference before treating a longer completion time as a problem. Choose alerts that tell someone what to do next: update expired credentials, inspect a changed product page or pause a queue that is repeatedly receiving rate limits. Keep a few redacted error examples to help with diagnosis. Review the dashboard's traffic usage alongside the completed page count, especially after changing retries or adding browser resources. A sudden increase can reveal repeated downloads that deserve attention.
Residential proxies provide household IPs with rotating connections or sticky sessions. Fusion Proxy's standard residential product supports country, state and city targeting and is billed by traffic used. Static ISP proxies provide assigned ISP-registered addresses, while datacenter proxies provide assigned server-network addresses. For both static products, check the countries and any city options currently offered in the order form.
Start with the requirement that would be hardest to change. For an IP allowlist, that is usually the fixed address. For a regional website test, it may be the country or city. For a large collection job, traffic usage and the site's response to the chosen IP type matter. Test a small set of actual target pages with the options that meet those requirements. Check the content returned, session behavior and cost for the expected run. Compare current plan duration and stock before ordering. If you need steady high-volume residential traffic with country targeting, also look at the unlimited speed-tier plans. Keep product differences visible in the comparison so you can see which setup the monthly price would actually provide.
Check current plans and available locations before ordering. For setup help, use the connection documentation or tell support which application and website you want to connect. Include any error message and the selected protocol, with the password removed.