Every URL on mewe.com, robots.txt included, is the same 15,465-byte shell with 17 words, to a plain HTTP client and to a rendered one, from the United States, Germany and the United Kingdom. The terms, which exist only after rendering, forbid data mining and robots. So the public data about MeWe is not on mewe.com: on 28 September 2026 the App Store record arrived in 1.0 second, the Google Play record in 4.7, twenty App Store reviews in 1.2. The setting for MeWe proxies is a collector and a country, not a browser.
The keyword is Magic cards, and the one data result is a licensed dataset
Search "mewe proxies" from the United States and Google assumes you play Magic: The Gathering. The first page is an r/EDH thread on reliable proxy-card sites, a Facebook MTG group, a proxying tutorial on YouTube. Autocomplete agrees: proxies for magic, proxies for mtg, mewe scrabble, mower scraper. In between sit mewe.com, its App Store listing, Wikipedia, a Quora thread on whether MeWe is really private, a Caddy reverse-proxy question, and an automation-forum post from someone whose bot cannot log in to MeWe after trying "different fingerprints, IPs, proxies".
One result is about data, and it tells you how MeWe data actually moves: a catalogue page pairing an Open Measures MeWe dataset with a social-media data pipeline. MeWe content reaches researchers through licensed feeds, not through fetching mewe.com. That matches what we measured. Here is the measurement, the clause that explains it, and the three surfaces that do answer.
mewe.com serves one 15,465-byte shell for every URL, including robots.txt
We fetched five paths on mewe.com over plain HTTP through a US residential exit. Four of them returned the same thing.
| Path | Content type | Bytes | Words | What it is |
|---|---|---|---|---|
| /robots.txt | text/html | 15,465 | 17 | the app shell, not a robots file |
| /terms | text/html | 15,465 | 17 | the app shell |
| /p/mewe (redirects to /mewe3747) | text/html | 15,465 | 17 | the app shell |
| /api/v2/me | text/plain | 51 | 0 | an Allow: OPTIONS reply; the API answers only a logged-in session |
The shell is a title, a meta description ("No Targeted Ads. No Spyware."), an Organization JSON-LD block, and a 17-word notice asking the visitor to enable JavaScript. There is no robots.txt at all: the request for it gets the shell with an HTML content type, so a crawler reading the file gets no rules, and MeWe's crawl policy is whatever its terms say. Then we audited the profile path with and without JavaScript from three countries.
| Exit | No-JS words | Rendered words | Rendered H1 | Audit time (both passes) |
|---|---|---|---|---|
| United States | 17 | 17 | none | 14.1 s |
| Germany | 17 | 17 | none | 12.0 s |
| United Kingdom | 17 | 49 | We're sorry | 7.8 s |
From the United States and Germany the render finished with the shell still on screen. From the United Kingdom it got further: the app booted, resolved the route, and produced its own "We're sorry" page, 49 words, because a logged-out visitor is not shown profiles. The full rendered fetch from the US weighed 1,928,383 bytes in 6.5 seconds and ended on /404 with the same 19 Markdown words as the shell. A logged-out browser on MeWe spends two megabytes to learn that there is nothing to read, which is the same shape as Bluesky's web app without Bluesky's open API behind it.
The terms say it in one line: no data mining, no robots
MeWe's Terms of Service exist only after rendering, at /cms/terms: 1,355,041 bytes, 11.8 seconds, 621 words. Three clauses cover this article. The licence MeWe grants you to use the site "does not include use of any data mining, robots or similar data gathering or extraction methods". The prohibited-conduct list says you may not "engage in spidering or harvesting, or participate in the use of software, including spyware, designed to collect data from the Site or Services, including about other MeWe users", nor "use automated methods to use the Site or Services". A separate section on MeWe Earnings bans "auto clicks, bots or other software" outright.
That is the line, and it is a short one. MeWe is a private network by design: no public profiles for logged-out visitors, no public API, an app whose reviews complain that the July 2026 release started asking existing members for age verification before showing posts. Reading mewe.com with a proxy is not something we help with, and there is nothing there to read. What is legitimately public about MeWe lives outside mewe.com, and that is where the measurement gets interesting.
MeWe's public numbers live in the app stores, and a collector reads them in a second
The App Store and Google Play listings are public, structured, per country, and they are how anyone tracking MeWe as a company, a competitor or a market signal actually measures it. We ran three collectors from the catalogue on 28 September 2026.
| Collector | Input | Rows | Seconds | What came back |
|---|---|---|---|---|
| app_store_apps | app id 918464474, country us | 1 | 1.0 | rating 4.44 from 294,231 reviews, version 3.0.28 of 22 September 2026, 228,026,368 bytes, developer Sgrouples, Inc., released 12 October 2014, 17+, "more than 700,000 groups", Premium at $6.49/month |
| google_play_apps | package com.mewe, country us | 1 | 4.7 | rating 4.05 from 187,176 reviews, 10M+ installs, Mature 17+, category Social |
| app_store_reviews | app id 918464474, country us, 20 results | 20 | 1.2 | reviews from 17 May to 25 August 2026 with rating, version, title, text and author |
The twenty reviews are a social-listening sample you cannot get from mewe.com: eleven one-star, one two-star, three three-star, five five-star. Five of the twenty are about the age-verification step introduced with release 3.0.20 in July 2026 (a driver's licence or a selfie before posts are shown), three about messaging becoming a paid feature, one about a paid subscription renewing on an account the app no longer recognised. Per country, per version, dated. That is the dataset for a competitor brief or a churn signal, and it costs $0.0005 per review on the collector page, $0.01 for the twenty.
Counting a gigabyte as 10^9 bytes, and using the per-GB prices on our pricing page, here is what the two routes cost:
| Read | Unit | Cost per unit | What you get |
|---|---|---|---|
| mewe.com shell, plain HTTP | 15,465 bytes (64,662 per GB) | $0.000012 on residential Basic $0.80/GB | 17 words, an Organization block |
| mewe.com profile path, rendered | 1,928,383 bytes (519 per GB) | $0.00154 on residential Basic $0.80/GB | the same 17 words, or a 49-word sorry page |
| App Store app record | 1 row | $0.0008 | rating, review count, version, size, description, screenshots |
| Google Play app record | 1 row | $0.006 | rating, review count, install band, content rating |
| App Store reviews | 1 row | $0.0005 | dated, rated, versioned review with text |
Ten thousand rendered fetches of mewe.com cost $15.40 and return nothing. Ten thousand App Store reviews cost $5 and return ten thousand dated, rated records. Telling you not to buy bandwidth for this network is the whole point of measuring it; the same cheap answer applied to Mastodon, where the API beat the render 700 to 1.
What a proxy is for on MeWe, and what it is not
The proxy has one job here: the country. App-store listings, ratings and reviews differ by storefront, and every collector above takes a country input that selects the local store and the exit at once. A brand tracking MeWe across the United States, Germany and the United Kingdom runs the same three collectors three times with three country codes and gets three review sets, three ratings, three version rollouts. That is geo-checking, and it is a per-request flag on the residential network.
What the proxy is not for is mewe.com itself. Logged-out, the site has nothing to read; logged-in, the terms forbid reading it by machine. The forum post on the SERP about a bot that cannot log in "with different fingerprints, IPs, proxies" is a person trying to do the thing the terms prohibit, and the answer is the same whether or not it works: we do not help with it. Public store data, pinned country, no browser.
The setting that works on MeWe
- Network: residential proxies, Basic line, $0.80/GB, used only to pin the store country. Nothing on mewe.com asked about our address across seven fetches from three countries; there was simply nothing to read.
- Fetch mode:
engine: tlsif you want the 15,465-byte shell for its Organization block and meta description; never rendered. Rendered, the profile path costs 1,928,383 bytes for 17 words from the United States and Germany and a 49-word sorry page from the United Kingdom. - Country: the storefront you are measuring. The three collectors above take
countryas input and it selects both the local store and the exit; the numbers we quote (4.44 from 294,231 reviews, 4.05 from 187,176) are the US storefronts on 28 September 2026. - When the proxy is not enough: it is never enough on MeWe, so start with the collectors. app_store_reviews returned 20 rows in 1.2 seconds, app_store_apps 1 row in 1.0 second, google_play_apps 1 row in 4.7 seconds, all pay per delivered row. The web scraping API is the tool for the licensed research feeds and the help centre, not for mewe.com profiles.
- Free tier: every account gets $2 of free API usage per month, which at $0.0005 per review is 4,000 App Store reviews before you pay anything.
Skip mewe.com, read the stores, pin the storefront country. That is the whole configuration for MeWe.